Potential fix for code scanning alert no. 3: Workflow does not contain permissions#27
Merged
Potential fix for code scanning alert no. 3: Workflow does not contain permissions#27
Conversation
…n permissions Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
security-reviewsecurity-review: No issues found No findings to report. |
dcramer
added a commit
that referenced
this pull request
Jan 29, 2026
Add explicit `permissions: contents: read` to both workflow examples in the setup docs to match PR #27's security fix. This ensures users following the docs create workflows with least-privilege permissions. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
dcramer
added a commit
that referenced
this pull request
Jan 30, 2026
Add explicit `permissions: contents: read` to both workflow examples in the setup documentation. PR #27 adds this security fix to the actual `.github/workflows/warden.yml` file, but the docs templates that users copy were missing it. This ensures users following the setup guide create workflows with least-privilege permissions from the start. Refs #27 --------- Co-authored-by: Claude Opus 4.5 <noreply@anthropic.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.
Potential fix for https://github.com/getsentry/warden/security/code-scanning/3
In general, the fix is to explicitly declare least‑privilege
permissionsfor the workflow or job so thatGITHUB_TOKENis restricted instead of inheriting broad defaults. For this workflow, we only need read access to repository contents (for checkout and reading metadata), because any write operations (comments, status updates, labels, etc.) should use the GitHub App token already being created.The best minimal fix is to add a
permissionsblock at the workflow root (top level, alongsidenameandon) withcontents: read. This applies to all jobs, includingreview, and does not change functional behavior other than limiting the inheritedGITHUB_TOKENcapabilities. No additional imports or methods are needed, only a YAML edit in.github/workflows/warden.ymlnear the top of the file. If later you discover that some step truly requires more scopes onGITHUB_TOKEN, you can selectively add them, but the safe default iscontents: read.Suggested fixes powered by Copilot Autofix. Review carefully before merging.