ci: declare workflow-level contents: read on 5 build/sanitizer workflows#393
Open
arpitjain099 wants to merge 1 commit into
Open
ci: declare workflow-level contents: read on 5 build/sanitizer workflows#393arpitjain099 wants to merge 1 commit into
contents: read on 5 build/sanitizer workflows#393arpitjain099 wants to merge 1 commit into
Conversation
Five CI workflows (ci, asan, tsan, code-style, ubsan) all run pure build and sanitizer checks. No GitHub API writes from the workflows themselves. Post-CVE-2025-30066 supply-chain hardening pattern. yaml.safe_load validated on each touched file. 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.
Five CI workflows (
ci,asan,tsan,code-style,ubsan) all run pure build and sanitizer checks. No GitHub API writes from the workflows.Same post-CVE-2025-30066 (
tj-actions/changed-files) hardening pattern. YAML validated locally withyaml.safe_loadon each touched file.Note
Low Risk
Low risk: CI-only change that tightens GitHub token permissions and should not affect build/test logic beyond potential permission-related checkout/tooling issues.
Overview
Adds workflow-level
permissions: contents: readto theci,asan,tsan,ubsan, andcode-styleGitHub Actions workflows to explicitly scope the defaultGITHUB_TOKENto read-only repository access.This is a hardening change aligned with least-privilege CI execution; no job steps or build/test behavior is otherwise modified.
Reviewed by Cursor Bugbot for commit af94e61. Bugbot is set up for automated code reviews on this repo. Configure here.