Potential fix for code scanning alert no. 10: Workflow does not contain permissions#57
Merged
EdGeraghty merged 1 commit intodevelopfrom Aug 23, 2025
Merged
Potential fix for code scanning alert no. 10: Workflow does not contain permissions#57EdGeraghty merged 1 commit intodevelopfrom
EdGeraghty merged 1 commit intodevelopfrom
Conversation
…in permissions Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Member
Author
|
Fixed #44 |
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/privacyint/docker-headscale/security/code-scanning/10
To fix the problem, you should add a
permissions:key to restrict the GITHUB_TOKEN permissions for this workflow. The least privilege required for the workflow should be specified. Given the current usage (checking out code, running tests, caching), the only necessary permission is typically read access to repository contents. You should addpermissions:at the root level (beforejobs:), settingcontents: read. This ensures that any job not needing additional permissions is restricted to read-only access. No additional imports, definitions, or other changes are required—just the addition of the permissions YAML block. The edit should be made near the start of the file, after thename:and beforeon:or directly beforejobs:.Suggested fixes powered by Copilot Autofix. Review carefully before merging.