Draft
Harden CI workflow token scope with explicit read-only permissions#34
Conversation
Co-authored-by: joelst <30506169+joelst@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix code scanning alert #3
Harden CI workflow token scope with explicit read-only permissions
Sep 3, 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
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.
This PR addresses code scanning alert #3 by removing implicit
GITHUB_TOKENpermission behavior in CI. The workflow now declares least-privilege permissions explicitly at workflow scope.Security hardening (CodeQL alert remediation)
permissionsblock in.github/workflows/ci.yml.contents: readto constrain token capabilities for all CI jobs unless explicitly overridden later.Scope of change