Skip to content

Rule Reference

SEC504lintai-ai-securitystableclaude_settingswarn

Claude settings: shared gh repo create permissions

Claude settings permissions allow `Bash(gh repo create:*)` 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 creation authority through `permissions.allow`.

Deterministic signal basis

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

Malicious corpus
claude-settings-gh-mutation-permissions
Benign corpus
claude-settings-gh-mutation-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

SEC504 / CLAUDE-GH-REPO-CREATE-PERMISSION

SEC504 flags shared Claude settings when permissions.allow grants blanket GitHub repository-creation authority.

Why It Matters

gh repo create provisions new remote repositories. In shared committed settings that is a high-agency mutation capability that should usually stay narrower than a default team-wide permission grant.

Trigger Shape

The rule triggers only when all of these are true:

  • the file is a detected Claude settings surface
  • the path is not fixture-like
  • permissions.allow contains the exact token Bash(gh repo create:*)

Clean Cases

These stay clean:

  • read-only repository commands such as Bash(gh repo view:*)
  • settings files that do not grant blanket repository creation
  • fixture-like examples under test or fixture paths

Example Trigger

json
{
  "permissions": {
    "allow": ["Bash(gh repo create:*)", "Read(*)"]
  }
}

Safer Example

json
{
  "permissions": {
    "allow": ["Bash(gh repo view:*)", "Read(*)"]
  }
}

How To Fix

Remove shared gh repo create permissions or replace them with narrower reviewed subcommands that keep repository creation under explicit user control.