Move CodeQL security-events permission to job level for better security #33
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 fixes the CodeQL workflow permissions to follow GitHub security best practices by moving the
security-events: write
permission from the workflow level to the job level.Changes Made
security-events: write
permission from workflow-level to job-level in.github/workflows/codeql-analysis.yml
contents: read
at workflow level (needed for checkout action)Before
After
Why This Change?
This change follows the principle of least privilege by scoping the
security-events: write
permission only to the specific job that needs it (the one runninggithub/codeql-action/analyze
), rather than making it available to the entire workflow.This pattern is already correctly implemented in the
ossf-scorecard.yml
workflow, and now both workflows that perform code scanning follow the same secure configuration.Fixes #32.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.