Skip to content

fix: restrict GITHUB_TOKEN permissions in CI workflows - #9

Merged
argosback merged 1 commit into
mainfrom
fix/workflow-permissions
Oct 18, 2026
Merged

argosback merged 1 commit into
mainfrom
fix/workflow-permissions

Conversation

@argosback

@argosback argosback commented Oct 18, 2026 •

Copy link
Copy Markdown
Member

Summary

  • Adds explicit least-privilege permissions blocks to ci.yml (contents: read) and sonarcloud.yml (contents: read, pull-requests: read)
  • Resolves CodeQL code scanning alerts 7 to 10 (actions/missing-workflow-permissions)
  • No version bump: workflow-only change; entry added under [Unreleased]

Verification

  • actionlint on all workflows
  • CI and SonarCloud workflows run on this PR with the restricted token

CodeQL flagged ci.yml and sonarcloud.yml for not declaring explicit
token permissions (actions/missing-workflow-permissions), leaving the
GITHUB_TOKEN with the repository default scope.

- ci.yml: add workflow-level permissions: contents: read
- sonarcloud.yml: add contents: read and pull-requests: read
- CHANGELOG.md: add entry under [Unreleased]
@sonarqubecloud

Copy link
Copy Markdown

@argosback
argosback merged commit 3fe5484 into main Oct 18, 2026
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant