← All permissions
Repository permission·dependabot_secrets:write
Dependabot secrets: Write
Tier 2 · Medium
Why Tier 2
Creates and overwrites the secrets Dependabot uses for private registries. It only replaces a credential: the registry URL lives in dependabot.yml or the organization's private registry settings, so a swap breaks updates rather than redirecting them.
- Target
- Repository
- Plane
- DataSecrets: Actions, environment, Dependabot, Codespaces and agent secrets, private registries and OIDC.
- Granted by
- Fine-grained PAT, GitHub App
- Available on
- Every setup
What it unlocks
2 REST endpoints need this permission. A few of them:
- PUT /repos/{owner}/{repo}/dependabot/secrets/{secret_name}
- DELETE /repos/{owner}/{repo}/dependabot/secrets/{secret_name}
Roles that include it
No built-in role includes it. Only tokens, Apps or custom roles can grant it.
Classic scopes that reach it
- T0repodocumented
Attack paths
No attack technique, escalation or incident on ghtier goes through this yet.
Other levels
GitHub Docs: Repository permissions for "Dependabot secrets"