ci: declare contents:read on test workflow#101
Merged
jcs090218 merged 1 commit intoMay 26, 2026
Conversation
Signed-off-by: Arpit Jain <arpitjain099@gmail.com>
jcs090218
approved these changes
May 14, 2026
Contributor
Author
|
@jcs090218 - PR has your approval and is green. Mergeable whenever convenient, thanks! |
Collaborator
|
Thank you for taking care of this! |
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.
Pins
.github/workflows/test.ymltopermissions: contents: readat the workflow level. The CI job sets up Node and Emacs, installs the package locally, then runs the prettier integration tests against the Emacs binary. No GitHub API calls beyond the initial checkout.CVE-2025-30066 (the March 2025
tj-actions/changed-filescompromise) is the supply-chain case for being explicit: a tampered third-party action readGITHUB_TOKENfrom workflow logs and the blast radius equalled whatever scope was issued. Capping atcontents: readhere keeps the runtime authority bounded regardless of the org or repo default, gives drift protection if that default ever widens, and registers with OpenSSF Scorecard's Token-Permissions check.YAML validated locally with
yaml.safe_load.