ci: declare contents:read on sync-ruby workflow#9547
Open
arpitjain099 wants to merge 1 commit into
Open
Conversation
Signed-off-by: Arpit Jain <arpitjain099@gmail.com>
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.
Adds
permissions: contents: readat the workflow level on.github/workflows/sync-ruby.yml. The job already usesactions/create-github-app-tokento mint a separate App token for the cross-repo dispatch, soGITHUB_TOKENitself only ever needs read access for the initial checkout. The workflow is already SHA-pinned and setspersist-credentials: false, which is great defensive hygiene; this is the small remaining piece.The motivation for being explicit even when the inherited default may already be reasonable is CVE-2025-30066 - the March 2025
tj-actions/changed-filescompromise where a tampered third-party action exfiltratedGITHUB_TOKENfrom workflow logs. The blast radius matched the issued scope. Pinning per workflow caps the runtime authority of every action in the chain regardless of the org default and survives a future default-widening change. OpenSSF Scorecard's Token-Permissions check also only credits explicit per-workflow declarations.YAML validated locally with
yaml.safe_load.