Skip to content

ci: scope down GitHub Token permissions #726

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

Closed
AdnaneKhan wants to merge 1 commit into from
Closed

ci: scope down GitHub Token permissions #726

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
3 changes: 3 additions & 0 deletions .github/workflows/codeql-analysis.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,9 @@ on:
push:
branches: [main]

permissions:
security-events: write
Copy link
Copy Markdown
Collaborator

@williazz williazz Dec 12, 2025

Choose a reason for hiding this comment

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

question: are we removing read permissions by only allowing security-events: write?

Copy link
Copy Markdown
Contributor Author

@AdnaneKhan AdnaneKhan Dec 12, 2025 •
edited
Loading

Choose a reason for hiding this comment

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

For public repositories read permissions on the GitHub Token are not required because the endpoints work without any AuthN/AuthZ, with the exception of unique keys like models: read (for AI inference with GitHub models) and packages: read (for workflows that run container jobs).


jobs:
analyze:
name: Analyze
Expand Down
Loading