ci: declare workflow-level contents: read on 8 test/fuzz workflows#1162
Open
arpitjain099 wants to merge 1 commit into
Open
ci: declare workflow-level contents: read on 8 test/fuzz workflows#1162arpitjain099 wants to merge 1 commit into
contents: read on 8 test/fuzz workflows#1162arpitjain099 wants to merge 1 commit into
Conversation
Pins the default GITHUB_TOKEN to contents: read on the 8 workflows in .github/workflows/ that don't actually need any write scope: - cifuzz.yml: OSS-Fuzz CI integration. - test-bench.yml: micro-benchmarks. - test-fuzzer.yml: standalone fuzzer. - test-linux.yml, test-macos.yml, test-windows.yml: build/test matrix per OS. test-linux.yml's coverallsapp/github-action step uses the GITHUB_TOKEN to identify with coveralls.io (token read for auth, not a GitHub API write), so contents: read is sufficient. - test-pkg-config.yml: pkg-config sanity check. - test-website.yml: website build check. deploy-website.yml is intentionally left implicit; it needs write scope for the gh-pages deploy. Motivation: CVE-2025-30066 (March 2025 tj-actions/changed-files compromise) exfiltrated GITHUB_TOKEN from workflow logs. Per-workflow caps bound runtime authority irrespective of repo or org default, give drift protection if the default ever widens, and are credited per-file by the OpenSSF Scorecard Token-Permissions check. YAML validated locally with yaml.safe_load. Signed-off-by: Arpit Jain <arpitjain099@gmail.com>
|
coverage: 99.162%. remained the same — arpitjain099:chore/declare-workflow-perms-readonly into uber:master |
isaacbrodsky
requested review from
ajfriend,
dfellis,
dmitryzv,
isaacbrodsky and
nrabinowitz
isaacbrodsky
approved these changes
May 19, 2026
dfellis
approved these changes
May 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pins the default
GITHUB_TOKENtocontents: readon the 8 workflows in.github/workflows/that don't actually need any write scope:cifuzz.yml: OSS-Fuzz CI integration.test-bench.yml: micro-benchmarks.test-fuzzer.yml: standalone fuzzer.test-linux.yml,test-macos.yml,test-windows.yml: build and test matrix per OS.test-linux.yml'scoverallsapp/github-actionstep uses theGITHUB_TOKENto identify with coveralls.io (token read for auth, not a GitHub API write), socontents: readis sufficient.test-pkg-config.yml: pkg-config sanity check.test-website.yml: website build check.deploy-website.ymlis intentionally left implicit; it needs write scope for the gh-pages deploy and is best declared by a maintainer.Why
CVE-2025-30066 (March 2025
tj-actions/changed-filessupply-chain compromise) exfiltratedGITHUB_TOKENfrom workflow logs and the leaked token retained whatever scope was issued at the workflow level. Pinning per workflow caps that runtime authority irrespective of the repo or org default, gives drift protection if the default ever widens, and is credited per-file by the OpenSSF ScorecardToken-Permissionscheck.YAML validated locally with
yaml.safe_loadon each touched file.