Skip to content

Rule Reference

SEC534lintai-ai-securitystableclaude_settingswarn

Claude settings: shared gh repo delete permissions

Claude settings permissions allow `Bash(gh repo delete:*)` in a shared committed config

Provider
lintai-ai-security
Surface
claude_settings
Scope
per_file
Tier
stable
Severity
warn
Confidence
high
Detection
structural
Remediation
message_only

Activation Model

Preset Membership

This rule is part of the builtin activation graph through these preset memberships.

Lifecycle

Stable Lifecycle Contract

State

stable_gated

Graduation rationale

Checks shared Claude settings for exact GitHub repository deletion authority through `permissions.allow`.

Deterministic signal basis

ClaudeSettingsSignals exact string detection for `Bash(gh repo delete:*)` inside permissions.allow on parsed Claude settings JSON.

Malicious corpus
claude-settings-gh-repo-release-delete-permissions
Benign corpus
claude-settings-gh-repo-release-delete-specific-safe
structured evidence required remediation reviewed
Canonical note

Structural stable rule intended as a high-precision check with deterministic evidence.

Nearby Signals

Related Rules

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.allow contains the exact token Bash(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.