Skip to content

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

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

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

Conversation

@arpitjain099
Copy link
Copy Markdown

Adds workflow-level permissions: contents: read to the check workflows in this repo (format-check, codeql-build, static-analysis where present). All run pure code checks; jobs that need higher scope can still override at job level.

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

All workflows just run pure checks. No GitHub API writes from workflows at workflow level. Job-level overrides for security-events on codeql remain.

Post-CVE-2025-30066 hardening pattern.

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

Closing in favor of #89 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. #89 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