Potential fix for code scanning alert no. 26: Workflow does not contain permissions#24
Merged
Conversation
…in permissions Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Review or Edit in CodeSandboxOpen the branch in Web Editor • VS Code • Insiders |
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/Codetoil/Platformer3D-Engine/security/code-scanning/26
Generally, this problem is fixed by adding an explicit
permissionsblock to the workflow (at the root or per-job) that grants only the minimal scopes needed, typicallycontents: readfor a basic CI job. This overrides potentially broader repository defaults and clearly documents what the workflow can do with theGITHUB_TOKEN.For this workflow, the best fix without changing existing functionality is to add a
permissionsblock at the workflow root (just belowname: Node.js CIand beforeon:). The steps use only standard actions that need read access to the repository (actions/checkout) and to artifacts (actions/upload-artifactdoes not rely oncontents: write), and do not require any write permissions. Therefore, settingpermissions: contents: readis sufficient and safest. No imports or additional definitions are required; this is a pure YAML configuration change in.github/workflows/node.js.yml.Suggested fixes powered by Copilot Autofix. Review carefully before merging.