Potential fix for code scanning alert no. 3: Workflow does not contain permissions#5
Merged
Potential fix for code scanning alert no. 3: Workflow does not contain permissions#5
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/pmalarme/github-secrets/security/code-scanning/3
In general, the fix is to explicitly limit
GITHUB_TOKENpermissions either at the workflow root (applies to all jobs) or per job, using the least privileges needed. Since this reusable workflow only echoes secrets/variables and writes to$GITHUB_STEP_SUMMARYand does not touch repository contents or make API mutations, it does not require write permissions; a minimal read-only permission set is sufficient.The best way to fix this without changing existing functionality is to add a
permissions:block at the top level of.github/workflows/reusable_workflow.yaml, directly under thename:(or beforeon:). This will apply to bothrun-reusable-workflowandrun-reusable-workflow-without-environment. A conservative minimal configuration that matches GitHub’s recommended pattern but keeps the token read-only is:This ensures the token cannot write to repository contents or other resources while still allowing read access if some future step (like
actions/checkout) is added. No imports or other code changes are needed; we only add this YAML block in the indicated region.Suggested fixes powered by Copilot Autofix. Review carefully before merging.