Skip to content

ci: declare workflow-level contents: read#63

Open
arpitjain099 wants to merge 1 commit into
solidjs:mainfrom
arpitjain099:chore/workflow-perms
Open

ci: declare workflow-level contents: read#63
arpitjain099 wants to merge 1 commit into
solidjs:mainfrom
arpitjain099:chore/workflow-perms

Conversation

@arpitjain099
Copy link
Copy Markdown

The CI workflow runs npm install + npm test on PR and push to main. No GitHub API writes, so workflow-level contents: read is the right ceiling for the default GITHUB_TOKEN.

Same least-privilege motivation as the post-CVE-2025-30066 hardening (the tj-actions/changed-files compromise exfiltrated default token scopes from caller workflow logs in March).

YAML validated locally.

The CI workflow runs npm install and npm test on PR and push to main. No GitHub API interaction beyond the checkout, so contents: read is sufficient at the workflow level.

CVE-2025-30066 (tj-actions/changed-files compromise) is the recent reminder that any token granted at trigger time can be exfiltrated if a downstream action is compromised. Per-workflow permissions caps the blast radius. yaml.safe_load validated locally.

Signed-off-by: Arpit Jain <arpitjain099@gmail.com>
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.

1 participant