Potential fix for code scanning alert no. 3: Workflow does not contain permissions#257
Open
Potential fix for code scanning alert no. 3: Workflow does not contain permissions#257
Conversation
…n 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/IABTechLab/trusted-server/security/code-scanning/3
In general, the fix is to explicitly restrict the
GITHUB_TOKENin this workflow to the minimal permissions required. Since all the jobs only need to read the repository contents (for checkout, dependency resolution, and running tools) and do not write back to GitHub, we can safely declarecontents: readat the top level of the workflow. Definingpermissionsat the workflow root applies to all jobs that don't have their ownpermissionsblock, which matches this file.Concretely, edit
.github/workflows/format.ymlto add apermissionsblock near the top, alongsidenameandon. For example, add:between the
nameandonkeys. No additional methods, imports, or steps are required; this only changes the token scope that GitHub automatically injects, without altering the existing job behavior.Suggested fixes powered by Copilot Autofix. Review carefully before merging.