Potential fix for code scanning alert no. 1063: Workflow does not contain permissions#77
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/1063
The best way to remediate this problem is to add an explicit
permissionsblock to either the root of the workflow or specifically to thepublishjob. Since the workflow appears to only require reading repository contents (to check out code) and does not appear to require write actions against the repo via the GITHUB_TOKEN, the minimum recommended block would bepermissions: contents: read. You should add this either as a workflow-level (at the top, beneathname:and before or afteron:) or job-level (directly underpublish:). To apply least privilege everywhere, it is best to set it at the workflow level, but setting it at the job level is also acceptable.Edit
.github/workflows/publish.ymland add:just after line 1 or 2.
Suggested fixes powered by Copilot Autofix. Review carefully before merging.