fix: restrict GitHub Actions workflow token permissions (OSSF least-privilege)#2662
Merged
fix: restrict GitHub Actions workflow token permissions (OSSF least-privilege)#2662
Conversation
Agent-Logs-Url: https://github.com/mikefarah/yq/sessions/1b5db5e2-af78-4289-a6e0-2e972fc68ef1 Co-authored-by: mikefarah <1151925+mikefarah@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix OSSF workflow token permissions
fix: restrict GitHub Actions workflow token permissions (OSSF least-privilege)
Apr 13, 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
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.
OSSF Scorecard flagged four workflows with no top-level
permissionsblock, meaning jobs inherit potentially broad default token permissions rather than the minimum required.Changes
codeql.yml— Added top-levelpermissions: {}. Job-level scoped permissions (actions: read,contents: read,security-events: write) were already correct.release.yml— Added top-levelpermissions: {}. Job-level scoped permissions (contents: write,id-token: write) were already correct.snap-release.yml— Added top-levelpermissions: {}and explicit job-levelcontents: read. Snap publishing uses theSTORE_LOGINsecret, notGITHUB_TOKEN.docker-release.yml— Added top-levelpermissions: {}and job-levelcontents: read+packages: write.packages: writeis required for pushing toghcr.ioviaGITHUB_TOKEN.test-yq.ymlandgo.ymlalready hadpermissions: contents: readat the top level and were not changed.