Potential fix for code scanning alert no. 1: Workflow does not contain permissions#1
Merged
Merged
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/ltvco/txpdf/security/code-scanning/1
In general, the fix is to declare an explicit
permissionsblock for the workflow or for the specific job, granting only the minimal scopes needed. For this workflow, the job checks out code, builds a Docker image, runsanchore/scan-action, and uploads a SARIF report viagithub/codeql-action/upload-sarif. None of these steps require write access to the repository viaGITHUB_TOKEN; they only need to read the contents. Therefore, we can safely setpermissions: contents: readat the workflow root so it applies to all jobs.Concretely, in
.github/workflows/grype.yml, add apermissions:section immediately after thename:(or just beforejobs:). This will ensure theGITHUB_TOKENhas only read access to repository contents when this workflow runs. No imports or additional methods are needed since this is a YAML configuration change only, and it does not alter the runtime behavior of the workflow other than tightening security.Suggested fixes powered by Copilot Autofix. Review carefully before merging.