Skip to content

Potential fix for code scanning alert no. 11: Workflow does not contain permissions #10

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 22, 2025
Merged

Potential fix for code scanning alert no. 11: Workflow does not contain permissions #10

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions .github/workflows/security.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,6 @@
name: Security Scan
permissions:
contents: read
Comment on lines 1 to +3
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Grant CodeQL required security-events permissions

Adding permissions: contents: read restricts the workflow token to contents only. The codeql job calls github/codeql-action/.github/workflows/codeql.yml@v3, which requires security-events: write (and typically actions: read, contents: read) to upload SARIF results. With the new top-level block, security-events remains unset (defaults to none), so CodeQL can no longer publish results and the workflow will fail or silently drop findings. Explicitly declare the full set of permissions the CodeQL reusable workflow expects rather than only contents: read.

Useful? React with 👍 / 👎.


on:
push:
Expand Down
Loading