Potential fix for code scanning alert no. 4: Workflow does not contain permissions#111
Merged
Potential fix for code scanning alert no. 4: Workflow does not contain permissions#111
Conversation
…n permissions Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
Pull request overview
This PR addresses CodeQL code scanning alert #4 by making the build job in the release workflow explicitly least-privileged instead of relying on inherited/default GITHUB_TOKEN permissions.
Changes:
- Add an explicit job-level
permissionsblock to thebuildjob. - Restrict
buildtocontents: read,actions: read, and explicitly disable OIDC withid-token: none.
💡 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.
Potential fix for https://github.com/Cleboost/Rustmius/security/code-scanning/4
Add an explicit
permissionsblock to thebuildjob in.github/workflows/release.ymlso it no longer relies on inherited defaults.Best fix here (without changing behavior): define job-level permissions for
buildas:contents: read(required for checkout)actions: read(safe minimal explicit access for actions metadata)id-token: none(explicitly deny if unused)This keeps the job least-privileged and satisfies CodeQL’s requirement for explicit permission limits.
Suggested fixes powered by Copilot Autofix. Review carefully before merging.