Potential fix for code scanning alert no. 1: Workflow does not contain permissions#191
Merged
Conversation
…n permissions Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
deflis
marked this pull request as ready for review
September 30, 2025 17:40
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/deflis/node-narou/security/code-scanning/1
To fix this issue, explicitly set a
permissionskey at the top (root) level of the workflow (just underneathname:and aboveon:) to restrict theGITHUB_TOKEN's default permissions to the minimum necessary. In most npm publish workflows, unless you are updating the repo or releases or creating pull requests, onlycontents: readis necessary (in fact, sometimes zero permissions works, but that can break someactions/checkoutversions, socontents: readis preferred as a safe and minimal default). This ensures the principle of least privilege is adhered to.Specifically:
permissions:block withcontents: readat the top of.github/workflows/publish-npm.yml.Suggested fixes powered by Copilot Autofix. Review carefully before merging.