ci: declare contents:read on ci.yaml workflow#191
Open
arpitjain099 wants to merge 1 commit into
Open
Conversation
Member
|
This change is |
Signed-off-by: Arpit Jain <arpitjain099@gmail.com>
arpitjain099
force-pushed
the
chore/declare-workflow-perms
branch
from
82e9ce9 to
be3ca56
Compare
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
2 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.
Adds a workflow-level
permissions: contents: readblock. The CI job checks out the repo, sets up Go viaactions/setup-go, and runsgo test/golangci-lint. No GitHub API calls outside the checkout.The runtime supply-chain threat that justifies the cap is CVE-2025-30066 (the March 2025
tj-actions/changed-filescompromise) - a tampered third-party action exfiltratedGITHUB_TOKENfrom workflow logs and the leaked token retained whatever scope was issued. Per-workflow caps bound the runtime authority of every action in the chain regardless of repo or org default, give drift protection if that default ever widens, and register with OpenSSF Scorecard's Token-Permissions check.YAML validated locally with
yaml.safe_load.