ci: declare contents:read on Java CI workflow#321
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 a workflow-level
permissions: contents: readblock to.github/workflows/ci-pull-request.yaml. The Java CI job only does checkout, JDK setup, andmvn verify; nothing here needs anything beyond read access to the repository.The motivation is supply-chain blast-radius capping. CVE-2025-30066 (the March 2025
tj-actions/changed-filescompromise) showed that a tampered third-party action can exfiltrateGITHUB_TOKENvia the workflow logs, and the leaked token retains whatever scope it was issued with. Pinning the workflow token tocontents: readbounds that runtime authority. The repo default may already be read-only, but an in-file declaration adds drift protection (a future change to the org or repo default can't silently widen this workflow) and lights up OpenSSF Scorecard's Token-Permissions check, which only counts explicit per-workflow declarations.YAML validated locally with
yaml.safe_load.