Potential fix for code scanning alert no. 15: Workflow does not contain permissions#35
Merged
Potential fix for code scanning alert no. 15: Workflow does not contain permissions#35
Conversation
…in 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
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/cortega26/polla/security/code-scanning/15
In general, this should be fixed by explicitly declaring a
permissionsblock that grants only the minimalGITHUB_TOKENscopes required by the workflow. Since this workflow primarily checks out code and does not appear to perform any write operations to the repository or other GitHub resources, the minimal safe baseline iscontents: read. Declaring this at the workflow root will apply to all jobs (test,ingest,publish) since none currently have their ownpermissionsblock.The best way to fix this without changing behavior is to add:
near the top of
.github/workflows/scrape.yml, at the root level (same indentation ason:andjobs:). This will constrain theGITHUB_TOKENto read-only repository contents, which is sufficient foractions/checkoutand other read-only operations in the current snippet. No additional imports or external methods are needed, as this is purely a workflow configuration change.Concretely:
.github/workflows/scrape.yml.permissionsblock after thename:line and before theon:block (e.g., after line 2, preserving blank lines as appropriate).Suggested fixes powered by Copilot Autofix. Review carefully before merging.