lintai docs

Appearance

Rule Reference

SEC388lintai-ai-securitygovernancehardeningpreviewclaude_settingswarn

Claude settings: shared git stash permissions

Claude settings permissions allow `Bash(git stash:*)` in a shared committed config

Public lane
governance
Category
hardening
Provider
lintai-ai-security
Scope
per-file
Surface
claude_settings
Tier
preview
Severity
warn
Confidence
high
Detection
structural
Remediation
message only
How to read this lane

Shared authority and workflow policy review.

How to read this category

Least-privilege, provenance, or operational hygiene signal.

Activation Model

Preset Activation

These presets explain where this rule appears in the product experience.

governancesidecar lane
claudesurface preset

Lifecycle

Stable Lifecycle Contract

State

stable

Graduation rationale

Checks shared committed Claude settings for exact `Bash(git stash:*)` authority.

Deterministic signal basis

ClaudeSettingsSignals exact permission detection for `Bash(git stash:*)` entries inside permissions.allow.

Malicious corpus
claude-settings-git-stash-permission
Benign corpus
claude-settings-git-stash-specific-safe
structured evidence required remediation reviewed
Canonical note

Structural preview rule; deterministic today, but the preview contract may still evolve.

Nearby Signals

Related Rules

SEC385Claude settings: shared git push permissionsClaude settings permissions allow `Bash(git push)` in a shared committed configgovernancehardeningclaude_settings
SEC386Claude settings: shared git checkout permissionsClaude settings permissions allow `Bash(git checkout:*)` in a shared committed configgovernancehardeningclaude_settings
SEC387Claude settings: shared git commit permissionsClaude settings permissions allow `Bash(git commit:*)` in a shared committed configgovernancehardeningclaude_settings
SEC399Claude settings: shared npx Bash permissionsClaude settings permissions allow `Bash(npx ...)` in a shared committed configgovernancehardeningclaude_settings
SEC406Claude settings: shared git add permissionsClaude settings permissions allow `Bash(git add:*)` in a shared committed configgovernancehardeningclaude_settings
SEC407Claude settings: shared git clone permissionsClaude settings permissions allow `Bash(git clone:*)` in a shared committed configgovernancehardeningclaude_settings

SEC388 / CLAUDE-GIT-STASH-PERMISSION ​

SEC388 flags shared Claude settings when permissions.allow grants the exact token Bash(git stash:*).

Why It Matters ​

git stash can hide in-progress work, rewrite the local working state, and make review harder when broad stash authority is inherited through a shared AI policy. This is safer as a narrower reviewed workflow than as a blanket shared permission.

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(git stash:*)

Clean Cases ​

These stay clean:

  • more specific command examples such as Bash(git stash push -u)
  • unrelated Git permissions like Bash(git status)
  • fixture-like examples under test or fixture paths

Example Trigger ​

json
{
  "permissions": {
    "allow": ["Bash(git stash:*)", "Read(*)"]
  }
}

Safer Example ​

json
{
  "permissions": {
    "allow": ["Bash(git status)", "Read(*)"]
  }
}

How To Fix ​

Remove shared Bash(git stash:*) permissions, or replace them with a narrower reviewed workflow that does not grant broad stash authority by default.