← All permissions
Repository permission·security_events:read
Code scanning alerts: Read
Tier 3 · Low
Why Tier 3
Reads code scanning alerts and analyses. Shows where the code is weak.
Data plane permissions start at Tier 2. This one is lowered for the reason above.
- Target
- Repository
- Plane
- DataCode security: Code scanning, Dependabot and secret scanning alerts, advisories, dismissals and bypasses.
- Granted by
- Fine-grained PAT, GitHub App, GITHUB_TOKEN
- Available on
- Every setup
- In a workflow
permissions: security-events: read
What it unlocks
12 REST endpoints need this permission. A few of them:
- GET /orgs/{org}/code-scanning/alerts
- GET /repos/{owner}/{repo}/code-scanning/ai-scan
- GET /repos/{owner}/{repo}/code-scanning/alerts
- GET /repos/{owner}/{repo}/code-scanning/alerts/{alert_number}
Roles that include it
- T0OwnerThe organization and every repository in it
- T0All-repository adminEvery repository in the organization
- T1WriteOne repository
- T1MaintainOne repository
- T1AdminOne repository
- T1Security managerThe organization and every repository in it
- T1All-repository writeEvery repository in the organization
- T1All-repository maintainEvery repository in the organization
- T2TriageOne repository
- T2All-repository triageEvery repository in the organization
- T3ReadOne repository
- T3All-repository readEvery repository in the organization
Classic scopes that reach it
- T1security_eventsdocumented
Attack paths
No attack technique, escalation or incident on ghtier goes through this yet.
Other levels
GitHub Docs: Repository permissions for "Code scanning alerts"