Potential fix for code scanning alert no. 10: Workflow does not contain permissions #467
Conversation
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
…in permissions Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
majanjua-amzn
approved these changes
Oct 14, 2025
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/aws-observability/aws-application-signals-test-framework/security/code-scanning/10
The fix is to add a
permissions:key at the top level of the workflow YAML file. Since none of the jobs in this workflow require write access (they perform checkouts, run linters, and build commands but do not push or alter repository content remotely), the minimal permission needed is read access to repository contents. This is done by settingpermissions: contents: readat the workflow root, which will apply to all jobs unless overridden—thus limiting theGITHUB_TOKENto read-only repository contents.This change should be made immediately following the
nameand before theon:trigger (i.e., after line 1 and before line 2).No additional imports or definitions are needed.
Suggested fixes powered by Copilot Autofix. Review carefully before merging.