Potential fix for code scanning alert no. 1: Workflow does not contain permissions#3
Merged
beckermarc merged 1 commit intomainfrom Oct 17, 2025
Merged
Potential fix for code scanning alert no. 1: Workflow does not contain permissions#3beckermarc merged 1 commit intomainfrom
beckermarc merged 1 commit intomainfrom
Conversation
…n permissions Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
rjayasinghe
approved these changes
Oct 17, 2025
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
2 participants
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/capire/xflights-java/security/code-scanning/1
To fix this issue, add a minimal explicit
permissionsblock at the top level of the workflow YAML file (.github/workflows/maven.yml), before thejobs:section. Since this workflow only checks out code and builds with Maven (reads source, runs tests, does not push, open issues, etc.), it suffices to grant onlycontents: read. This restricts theGITHUB_TOKENto the least privilege needed and avoids unintended write access. You do not need to modify existingjobsorsteps. Ensure the block uses correct YAML indentation.Suggested fixes powered by Copilot Autofix. Review carefully before merging.