Potential fix for code scanning alert no. 5: Workflow does not contain permissions#1641
Merged
kevinherron merged 1 commit into1.0from Nov 3, 2025
Merged
Potential fix for code scanning alert no. 5: Workflow does not contain permissions#1641kevinherron merged 1 commit into1.0from
kevinherron merged 1 commit into1.0from
Conversation
…n permissions Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.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/eclipse-milo/milo/security/code-scanning/5
The fix is to explicitly restrict the permissions for the workflow to the minimal set required. The workflow runs Maven verification and checks out code, which only requires the workflow to read repository contents, not write. Thus, adding a
permissions:block withcontents: readat the root of the workflow is sufficient and adheres to the principle of least privilege. The most robust way is to insert a block likepermissions: contents: readat the top-level, just belowname:(line 2 or 3), before theon:block.Suggested fixes powered by Copilot Autofix. Review carefully before merging.