← All permissions
Repository permission·artifact_metadata:read
Artifact metadata: Read
Tier 3 · Low
Why Tier 3
Reads artifact deployment records.
Data plane permissions start at Tier 2. This one is lowered for the reason above.
- Target
- Repository
- Plane
- DataReleases and packages: Packages, attestations and artifact metadata.
- Granted by
- Fine-grained PAT, GitHub App, GITHUB_TOKEN
- Available on
- Free, Team, Enterprise Cloud, EMU
- In a workflow
permissions: artifact-metadata: read
What it unlocks
3 REST endpoints need this permission. A few of them:
- GET /orgs/{org}/artifacts/metadata/deployment-record/cluster/{cluster}/jobs/{job_id}
- GET /orgs/{org}/artifacts/{subject_digest}/metadata/deployment-records
- GET /orgs/{org}/artifacts/{subject_digest}/metadata/storage-records
Roles that include it
No built-in role includes it. Only tokens, Apps or custom roles can grant it.
Classic scopes that reach it
No classic scope reaches it. Only fine-grained PATs, Apps or GITHUB_TOKEN can grant it.
Attack paths
No attack technique, escalation or incident on ghtier goes through this yet.