Potential fix for code scanning alert no. 4: Workflow does not contain permissions#15
Merged
prashanthvarma merged 1 commit intomainfrom Feb 4, 2026
Merged
Potential fix for code scanning alert no. 4: Workflow does not contain permissions#15prashanthvarma 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/4
In general, this issue is fixed by explicitly declaring a
permissionsblock that limits theGITHUB_TOKENto the least privilege necessary. For a linting/type-checking workflow that only needs to check out and read code,contents: readis normally sufficient. Declaring this at the workflow root applies to all jobs that do not override it; if some jobs need additional scopes they can define their ownpermissionsblocks.For this specific workflow, the simplest and safest fix without changing behavior is to add a root-level
permissionsblock specifying read-only access to repository contents. This will apply to bothflake8andmypyjobs. No steps in the shown code need write access to the repo, issues, or pull requests, so we only grantcontents: read. Concretely, in.github/workflows/lint.yml, insert:after the
on:block and beforejobs:. No additional imports or other definitions are required.Suggested fixes powered by Copilot Autofix. Review carefully before merging.