ci: declare contents:read on lint_and_coverage workflow#490
Open
arpitjain099 wants to merge 1 commit into
Open
ci: declare contents:read on lint_and_coverage workflow#490arpitjain099 wants to merge 1 commit into
arpitjain099 wants to merge 1 commit into
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.
Pins
.github/workflows/lint_and_coverage.ymltopermissions: contents: readat the workflow level. The job clones, sets up Python, installs deps, runs lint and pytest with coverage. Nothing in that flow calls a GitHub API that needs write access.The supply-chain motivation behind explicit per-workflow scopes is CVE-2025-30066 (the March 2025
tj-actions/changed-filescompromise) - a tampered third-party action exfiltratedGITHUB_TOKENvia workflow logs, and the blast radius equalled whatever scope the token was issued with. A workflow-level cap ofcontents: readkeeps that bounded regardless of what the repo or org default happens to be at any given moment, and survives a future default-widening change. The block also registers with OpenSSF Scorecard's Token-Permissions check, which only credits explicit declarations.Validated locally with
yaml.safe_load.