Potential fix for code scanning alert no. 5: Workflow does not contain permissions#261
Open
Potential fix for code scanning alert no. 5: Workflow does not contain permissions#261
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
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/5
To fix the problem, explicitly restrict the
GITHUB_TOKENpermissions for this workflow instead of relying on repository/organization defaults. Since all three jobs only need to read the repository contents and do local formatting/linting, the minimal required permission iscontents: read.The best way to do this without changing existing functionality is to add a single top‑level
permissionsblock in.github/workflows/format.yml, right after theon:section and beforejobs:. This will apply to all jobs in the workflow because none of them currently define their ownpermissions. Concretely, insert:at the root level (same indentation as
on:andjobs:). No additional imports, methods, or other definitions are needed; this is a pure YAML configuration change that does not affect how the steps run, only the scope of theGITHUB_TOKEN.Suggested fixes powered by Copilot Autofix. Review carefully before merging.