Potential fix for code scanning alert no. 1: Workflow does not contain permissions #131
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
…n permissions Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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/tbroadley/spellchecker-cli/security/code-scanning/1
To fix the problem, we need to explicitly restrict the permissions for the GITHUB_TOKEN in the workflow. The CI job in this workflow only checks out code, sets up Node.js, installs dependencies, and runs scripts—none of these require write access to repository contents, pull requests, or other scopes. Thus, the minimal permission required is
contents: read, which allows the workflow to read the repository contents. This should be set in the workflow file either at the root level (affecting all jobs by default), or on individual jobs. The best and most maintainable way is to add it to the root of the file, just after thenamedeclaration and beforeon:.No imports, definitions, or additional configuration are needed, just a single YAML block added.
Suggested fixes powered by Copilot Autofix. Review carefully before merging.