Potential fix for code scanning alert no. 12: Workflow does not contain permissions #64
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/aws/aws-secretsmanager-caching-python/security/code-scanning/12
To fix the problem, add a
permissions
block to the workflow to explicitly set the minimal required permissions for theGITHUB_TOKEN
. The best practice is to setcontents: read
at the workflow level, which covers most use cases for CI workflows that only need to check out code and run tests. If any step requires additional permissions (such as uploading coverage reports to a pull request), those can be added as needed. In this case, since the workflow uploads coverage to Codecov (which does not require write access to the repository),contents: read
is sufficient. The change should be made at the top level of the workflow file, just after thename
key and before theon
key.Suggested fixes powered by Copilot Autofix. Review carefully before merging.