Potential fix for code scanning alert no. 11: Workflow does not contain permissions#580
Merged
Potential fix for code scanning alert no. 11: Workflow does not contain permissions#580
Conversation
…in permissions Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Slashgear
temporarily deployed
to
preview-pr-580
GitHub Actions
Inactive
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/lyonjs/lyonjs.github.com/security/code-scanning/11
To fix the problem, explicitly restrict
GITHUB_TOKENpermissions in the workflow, granting only what is required. These jobs do not call the GitHub REST/GraphQL APIs or push to the repo; they only need to read workflow metadata (github.*context) and write to$GITHUB_STEP_SUMMARY, which works withcontents: read. Therefore, we can safely set minimal read-only permissions for both jobs.The best fix without changing existing behavior is to add a
permissionsblock at the workflow root so it applies to all jobs. In.github/workflows/deploy-cleanup.yml, insert, aftername: 🧹 Cleanupand beforeon:, a block like:This limits
GITHUB_TOKENto read-only repository contents, which is sufficient for accessing the workflow’s context and for using the step summary. No additional imports or code changes are needed; only the YAML workflow header is updated.Suggested fixes powered by Copilot Autofix. Review carefully before merging.