ci: add explicit permissions block to fix CodeQL alerts - #89
Merged
Merged
Conversation
…sions alerts Three CodeQL Medium alerts flagged that the workflow had no explicit permissions block, leaving jobs with the default (which can be write-all on some orgs). Pinning to contents: read at the workflow level closes all three alerts and follows GitHub's principle-of-least-privilege guidance for CI workflows.
Contributor
There was a problem hiding this comment.
Pull request overview
This PR addresses GitHub CodeQL “Workflow does not contain permissions” alerts by explicitly setting a least-privilege default token scope for the CI workflow, ensuring jobs cannot write to repository contents.
Changes:
- Add a workflow-level
permissionsblock grantingcontents: readin.github/workflows/ci.yml.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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
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.
Summary
permissions: contents: readat the workflow level in.github/workflows/ci.ymlcontents: readis the correct least-privilege grantWhy
GitHub Actions defaults to
contents: writein some org configurations. Explicitly scoping toreadprevents any job in this workflow from accidentally (or maliciously, via a compromised action) writing to the repo.