Potential fix for code scanning alert no. 1064: Workflow does not contain permissions#78
Merged
HosseinNejatiJavaremi merged 1 commit intomasterfrom Aug 28, 2025
Merged
Conversation
…tain 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/SyntaxArc/ArchiPy/security/code-scanning/1064
The best way to fix this problem is to add a
permissionsblock at the appropriate level in the workflow file to limit the permissions of GITHUB_TOKEN to only what is required. Since the lint job only needs to read the code (e.g., to check out files, gather changed files, run the linter), it does not need write permissions. Therefore, addingpermissions: contents: readeither at the workflow root (to apply to all jobs) or within thelintjob (to apply only there) is ideal. For clarity and future extensibility, placing it at the job-level ensures explicitness, but root-level is also acceptable if there’s only one job. You'll need to insert:either just after
name: Lint(root-level), or on line 11, beforeruns-on: ubuntu-latest(job-level).Suggested fixes powered by Copilot Autofix. Review carefully before merging.