lintai docs

Appearance

Rule Reference

SEC538lintai-ai-securitystableclaude_settingswarn

Claude settings: shared gh repo edit permissions

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

previewmembership
claudemembership

Lifecycle

Stable Lifecycle Contract

State

stable_gated

Graduation rationale

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

Deterministic signal basis

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

Malicious corpus
claude-settings-gh-repo-edit-release-create-permissions
Benign corpus
claude-settings-gh-repo-edit-release-create-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

SEC362Claude settings: wildcard Bash permissionsClaude settings permissions allow `Bash(*)` in a shared committed configclaude_settingsstable
SEC364Claude settings: bypassPermissions default modeClaude settings set `permissions.defaultMode` to `bypassPermissions` in a shared committed configclaude_settingsstable
SEC367Claude settings: wildcard WebFetch permissionsClaude settings permissions allow `WebFetch(*)` in a shared committed configclaude_settingsstable
SEC369Claude settings: wildcard Write permissionsClaude settings permissions allow `Write(*)` in a shared committed configclaude_settingsstable
SEC372Claude settings: wildcard Read permissionsClaude settings permissions allow `Read(*)` in a shared committed configclaude_settingsstable
SEC373Claude settings: wildcard Edit permissionsClaude settings permissions allow `Edit(*)` in a shared committed configclaude_settingsstable

SEC538 / CLAUDE-GH-REPO-EDIT-PERMISSION ​

SEC538 flags shared Claude settings when permissions.allow grants blanket GitHub repository settings mutation authority through gh repo edit.

Why It Matters ​

gh repo edit can change visibility, features, merge settings, and other repository controls. 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 edit:*)

Clean Cases ​

  • narrower read-only grants such as Bash(gh repo view:*)
  • settings files without blanket repository edit access
  • fixture-like examples under test or fixture paths

Example Trigger ​

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

Safer Example ​

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

How To Fix ​

Remove shared gh repo edit permissions or replace them with narrower reviewed commands that keep repository settings mutation under explicit user control.