Skip to content

ci: declare workflow-level contents: read on 3 check workflows#165

Closed
arpitjain099 wants to merge 1 commit into
nasa:devfrom
arpitjain099:chore/declare-workflow-perms
Closed

ci: declare workflow-level contents: read on 3 check workflows#165
arpitjain099 wants to merge 1 commit into
nasa:devfrom
arpitjain099:chore/declare-workflow-perms

Conversation

@arpitjain099
Copy link
Copy Markdown

Three check workflows (format-check, codeql-build, static-analysis) just run code checks. No GitHub API writes from the workflows. Workflow-level contents: read is the right cap.

Same post-CVE-2025-30066 (tj-actions/changed-files) hardening pattern. YAML validated locally.

format-check, codeql-build, static-analysis are pure check workflows. No GitHub API writes from the workflows themselves. Workflow-level contents: read is appropriate.

Post-CVE-2025-30066 hardening pattern. yaml.safe_load validated.

Signed-off-by: Arpit Jain <arpitjain099@gmail.com>
@arpitjain099
Copy link
Copy Markdown
Author

Closing in favor of #164 to avoid duplicate/overlapping permissions PRs in this repo. The extra workflow this PR touched needs write scopes (CodeQL, auto-update, or a user/issue responder), so it should not get a blanket contents: read; I am leaving that to the maintainers. #164 hardens the read-only workflows here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants