Appearance
SEC534 / CLAUDE-GH-REPO-DELETE-PERMISSION
SEC534 flags shared Claude settings when permissions.allow grants blanket GitHub repository deletion authority through gh repo delete.
Why It Matters
gh repo delete can permanently remove repositories. In a shared committed settings file that is broader than most teams want to delegate by default.
Trigger Shape
- the file is a detected Claude settings surface
- the path is not fixture-like
permissions.allowcontains the exact tokenBash(gh repo delete:*)
Clean Cases
- narrower read-only grants such as
Bash(gh repo view:*) - settings files without blanket repository deletion access
- fixture-like examples under test or fixture paths
Example Trigger
json
{
"permissions": {
"allow": ["Bash(gh repo delete:*)", "Read(*)"]
}
}Safer Example
json
{
"permissions": {
"allow": ["Bash(gh repo view:*)", "Read(*)"]
}
}How To Fix
Remove shared gh repo delete permissions or replace them with narrower reviewed commands that keep repository deletion under explicit user control.