Restrict the GitHub token permissions only to the required ones; this way, even if the attackers will succeed in compromising your workflow, they won’t be able to do much.
- Included permissions for the action. https://github.com/ossf/scorecard/blob/main/docs/checks.md#token-permissions
https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#permissions
https://docs.github.com/en/actions/using-jobs/assigning-permissions-to-jobs
[Keeping your GitHub Actions and workflows secure Part 1: Preventing pwn requests](https://securitylab.github.com/research/github-actions-preventing-pwn-requests/)
Signed-off-by: naveen <172697+naveensrinivasan@users.noreply.github.com>
+permissions:
+ contents: read
+
+ permissions:
+ contents: write # for Git to git push
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
+permissions:
+ contents: read
+
jobs:
# Check Code style quickly by running `rustfmt` over all code
rustfmt:
jobs:
# Check Code style quickly by running `rustfmt` over all code
rustfmt:
sh linkcheck.sh --all cargo
success:
sh linkcheck.sh --all cargo
success:
+ permissions:
+ contents: none
name: bors build finished
needs: [docs, rustfmt, test, resolver, build_std]
runs-on: ubuntu-latest
name: bors build finished
needs: [docs, rustfmt, test, resolver, build_std]
runs-on: ubuntu-latest
steps:
- run: echo ok
failure:
steps:
- run: echo ok
failure:
+ permissions:
+ contents: none
name: bors build finished
needs: [docs, rustfmt, test, resolver, build_std]
runs-on: ubuntu-latest
name: bors build finished
needs: [docs, rustfmt, test, resolver, build_std]
runs-on: ubuntu-latest