Potential fix for code scanning alert no. 1: Workflow does not contain permissions#17
Merged
prashanthvarma merged 1 commit intomainfrom Feb 4, 2026
Merged
Potential fix for code scanning alert no. 1: Workflow does not contain permissions#17prashanthvarma merged 1 commit intomainfrom
prashanthvarma merged 1 commit intomainfrom
Conversation
…n permissions Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com> Signed-off-by: Prashanth Varma Manthena <me@prashanthvarma.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/Graphiant-Inc/graphiant-sdk-python/security/code-scanning/1
In general, the fix is to add an explicit
permissions:block to the workflow (either at the root, applying to all jobs, or inside the specific job) and restrictGITHUB_TOKENto the minimal needed scopes. For this build-only workflow, the job just checks out code, sets up Python, installs dependencies, builds the package, uploads artifacts, and verifies output; none of these require write access to the repository or other resources viaGITHUB_TOKEN. Therefore, we can setcontents: readand omit all other permissions, which default tonone.The best way to fix this without altering behavior is to add a root-level
permissions:block immediately after thename: Build SDKline, specifyingcontents: read. This will apply to all jobs in the workflow (currently justbuild) and does not interfere with any of the steps, which only read from the repository. No additional imports or methods are needed because this is configuration-only. No further changes to steps, triggers, or actions are required.Suggested fixes powered by Copilot Autofix. Review carefully before merging.