ci: set least-privilege GITHUB_TOKEN permissions#1041
Open
Alb3e3 wants to merge 1 commit into
Open
Conversation
Add a workflow-level `permissions: { contents: read }` block. The
affected workflow(s) only build, test, and/or fuzz the project; no job
writes to the repository or other GitHub resources, so read-only is the
correct least-privilege scope for the default GITHUB_TOKEN.
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
1 participant
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.
What
Adds a workflow-level
permissions: { contents: read }block to the affected workflow(s).Why
Without an explicit
permissions:block, these workflows run with the broad defaultGITHUB_TOKENscopes. The affected workflows only build, test, and/or fuzz the project — no job writes to the repository, releases, packages, or any other GitHub resource. Restricting the token tocontents: readfollows the principle of least privilege and limits the blast radius if any build/test/fuzz step (or a dependency it pulls in) were compromised. This matches GitHub-recommended and OpenSSF Scorecard "Token-Permissions" hardening guidance.Scope
permissionsblock per affected workflow.git diff --checkclean.Disclosure: I used AI assistance while preparing this change. The diff is small and I have reviewed it for correctness.