chore(ci): least-privilege top-level permissions on release/codeql workflows - #66
Merged
Merged
Conversation
…odeql workflows codeql.yml, release-nestjs.yml, and release-docker.yml had no top-level `permissions:` block (OpenSSF Scorecard TokenPermissions, high). Add a restrictive `contents: read` default; each job already declares the elevated permissions it needs (packages:write / contents:write / id-token:write / security-events:write), which override the default. No behavior change; quiets the recurring code-scanning noise so a real alert can't hide behind it. Co-Authored-By: Claude Opus 4.8 (1M context) <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.
codeql.yml,release-nestjs.yml, andrelease-docker.ymlhad no top-levelpermissions:block — the OpenSSF Scorecard TokenPermissions (high) finding, and the main source of the recurring red code-scanning check on PRs (which nearly let a real alert hide on #64).Adds a least-privilege
permissions: contents: readdefault to each. No behavior change — every job already declares the elevated permissions it needs (packages:write/contents:write/id-token:write/security-events:write), which override the top-level default.(Skipped the mass SHA-pinning of GitHub-owned actions — higher churn, lower value — as a separate optional pass.)
🤖 Generated with Claude Code