Skip to content

ci: cap GITHUB_TOKEN to contents: read#1863

Merged
aduh95 merged 1 commit into
nodejs:mainfrom
arpitjain099:chore/declare-workflow-perms
May 26, 2026
Merged

ci: cap GITHUB_TOKEN to contents: read#1863
aduh95 merged 1 commit into
nodejs:mainfrom
arpitjain099:chore/declare-workflow-perms

Conversation

@arpitjain099
Copy link
Copy Markdown
Contributor

Pins the default GITHUB_TOKEN to contents: read at workflow level. No GitHub API writes from the workflow.

Post-CVE-2025-30066 hardening pattern. YAML validated locally.

Workflow runs checks only; no GitHub API writes. Post-CVE-2025-30066 hardening pattern.

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

@aduh95 aduh95 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

FWIW it's already set as read-only in the repo settings, but having it set explicitly in the YAML is certainly fine and will cover forks as well

@aduh95 aduh95 merged commit 237575d into nodejs:main May 26, 2026
1 check passed
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