Potential fix for code scanning alert no. 13: Workflow does not contain permissions#55
Closed
Potential fix for code scanning alert no. 13: Workflow does not contain permissions#55
Conversation
…in 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
2 participants
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/cinode/go/security/code-scanning/13
The fix involves explicitly adding a
permissionskey to assign the least privilege required for the workflow. In this workflow, write permissions to repository contents or other resources are not necessary: we only need to read the code to run tests/check coverage. Therefore, we should setpermissions: contents: readeither at the top-level of the workflow, or at the job level. If it's possible that another job would be added in the future requiring different permissions, add it at the job level. Since there's only one job (tests), adding at the job level directly above thestrategy:key is sufficient and matches the line highlighted by CodeQL.Specifically, in the
.github/workflows/tests.ymlfile, add the following immediately after thetests:job definition and beforestrategy::No imports, definitions, or other changes required.
Suggested fixes powered by Copilot Autofix. Review carefully before merging.