Add explicit permissions to GitHub workflows #2140
Merged
Conversation
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
Fix code scanning alert about unlimited permissions by applying the principle of least privilege to all workflow jobs. Each job now has only the permissions it actually needs: - Build, test, publish, and compat jobs get contents: read - publish-docs keeps contents: write (needs to push to gh-pages) - rules workflow gets empty permissions (no repo access needed) Committed-By-Agent: claude
mbroshi-stripe
requested review from
prathmesh-stripe
and removed request for
a team
prathmesh-stripe
approved these changes
Jan 12, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Why?
Fix code scanning alerts about unlimited permissions in GitHub workflows. By default, workflows have read/write access to all scopes, which is a security concern. This change applies the principle of least privilege.
What?
permissions: {}at workflow level to restrict default permissionscontents: readpermission to each job that needs repository accesspublish-docsjob retainscontents: writeas it needs to push to gh-pagesrulesworkflow gets empty permissions as it only runs shell scriptsSee Also