Potential fix for code scanning alert no. 1: Workflow does not contain permissions #123
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
Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
fhonza
approved these changes
Nov 20, 2025
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/DCSO/fever/security/code-scanning/1
To fix the problem, you should add a
permissions:block to restrict the GITHUB_TOKEN in the workflow to the least privileges necessary. Since the workflow is only checking out code, installing dependencies, building, and running tests, the minimum required iscontents: read. This block should be added to the job (build:) level to restrict permissions only for this job (you could also add it at the root, but per the warning and context, adding it to the job is best practice and demonstrates targeted permission scoping). No changes to steps, imports, or other definitions are necessary: simply add the permissions block.Suggested fixes powered by Copilot Autofix. Review carefully before merging.