Potential fix for code scanning alert no. 298: Workflow does not contain permissions#335
Merged
Conversation
…ain permissions Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
NickLetts2
added a commit
that referenced
this pull request
Jun 1, 2026
Potential fix for code scanning alert no. 298: Workflow does not contain permissions
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
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/NickLetts2/Curvit/security/code-scanning/298
Add an explicit
permissionsblock to the workflow so theGITHUB_TOKENis constrained to least privilege.Best fix here: set workflow-level permissions to
contents: read, since the job usesactions/checkoutand local script execution only, with no evidence of needing write scopes.Where to change:
.github/workflows/ci-observability.ymlon:triggers block and beforejobs:(or alternatively under the specific job).Workflow-level is best here because there is only one job and this documents secure defaults clearly.
No imports, methods, or additional definitions are needed (YAML config-only change).
Suggested fixes powered by Copilot Autofix. Review carefully before merging.