Potential fix for code scanning alert no. 3: Workflow does not contain permissions#778
Draft
mykaul wants to merge 1 commit intoscylla-4.xfrom
Draft
Potential fix for code scanning alert no. 3: Workflow does not contain permissions#778mykaul wants to merge 1 commit intoscylla-4.xfrom
mykaul wants to merge 1 commit intoscylla-4.xfrom
Conversation
… no. 3: Workflow does not contain permissions Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
dkropachev
approved these changes
Jan 1, 2026
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/scylladb/java-driver/security/code-scanning/3
In general, the fix is to explicitly set
permissionsfor the workflow or individual jobs so that theGITHUB_TOKENhas only the minimal required privileges. Since the jobs here only check out code, use caches, and run Maven/Make, they only need read access to the repository contents; they do not need to write to the repo, issues, or PRs.The single best fix with no functional change is to add a top-level
permissionsblock (so it applies to all jobs) just after theon:triggers and beforejobs:. This block should setcontents: read, which is the minimal reasonable permission for workflows that need to check out the code. No changes are needed inside individual jobs or steps.Concretely, in
.github/workflows/tests@v1.yml, insert:between the
workflow_dispatch:line and thejobs:key. No imports or other definitions are required.Suggested fixes powered by Copilot Autofix. Review carefully before merging.