Potential fix for code scanning alert no. 7: Workflow does not contain permissions#112
Merged
Conversation
…ntain permissions Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.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/abelcheung/types-lxml/security/code-scanning/7
To fix the problem, add an explicit
permissionsblock to thebuildjob so that the GITHUB_TOKEN is restricted instead of inheriting repository defaults. Since thebuildjob only dispatches a reusable workflow and passesgitref, it almost certainly needs at most read access to repository contents. A safe, minimal starting point consistent with GitHub’s recommendations ispermissions: contents: read.Concretely, in
.github/workflows/release.yml, underjobs: build:, insert apermissions:mapping beforeuses:. This will apply only to thebuildjob and will not affect the other jobs, which already declare their own permissions. No additional methods, imports, or definitions are needed since this is just a YAML configuration change.Suggested fixes powered by Copilot Autofix. Review carefully before merging.