Fix for code scanning alert: Workflow does not contain permissions #82
Open
ScottBrenner wants to merge 1 commit intoVantaInc:mainfrom
Open
Fix for code scanning alert: Workflow does not contain permissions #82ScottBrenner wants to merge 1 commit intoVantaInc:mainfrom
ScottBrenner wants to merge 1 commit intoVantaInc:mainfrom
Conversation
…n permissions Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
c841169 to
aabdc08
Compare
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.
In general, the fix is to add an explicit
permissionsblock to the workflow (at the top level or per-job) restricting theGITHUB_TOKENto the minimum needed. Here, the jobs only need to check out the repository, which requirescontents: read. They don’t need to write to the repo or interact with issues, PRs, or other resources.The best fix with minimal functional impact is to add a root-level
permissionsblock right under thename:(oron:) key in.github/workflows/main.yml, settingcontents: read. This automatically applies to bothbuild-ubuntuandbuild-macosjobs, since they don’t have their ownpermissionsblocks. No changes to steps or actions are needed. Concretely, you should edit.github/workflows/main.ymlso that after line 1 (name: CI), you insert:This satisfies CodeQL’s recommendation and least-privilege principles without changing workflow behavior.
Suggested fixes powered by Copilot Autofix. Review carefully before merging.