Potential fix for code scanning alert no. 2: Workflow does not contain permissions#4
Merged
Potential fix for code scanning alert no. 2: Workflow does not contain permissions#4
Conversation
…n permissions Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com> Signed-off-by: Remy Duijsens <remyduijsens@gmail.com>
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/HauntedMC/DataProvider/security/code-scanning/2
In general, fix this by explicitly defining a
permissionsblock to restrict theGITHUB_TOKENto the minimal scope needed. This can be placed at the workflow root (applies to all jobs without their ownpermissions) or on individual jobs.For this workflow, the single best fix without changing functionality is to add a root-level
permissionsblock after theon:section (or beforejobs:). The job only checks out code, sets up Java, runs Maven tests, and uploads artifacts; these require only read access to repository contents. Therefore we can safely set:Edit
.github/workflows/ci-tests-and-coverage.ymlbetween theon:block and thejobs:block, inserting thepermissionsmapping. No imports, methods, or other definitions are needed, as this is declarative YAML configuration only.Suggested fixes powered by Copilot Autofix. Review carefully before merging.