Skip to main content
statuslinesSource-backed

git-secrets Environment Risk Statusline

Claude Code statusline that surfaces sensitive environment-file risk and can optionally run git-secrets as a local pre-commit-style scanner.

by MkDev11·added 2026-06-04·
Language:bash
Review first review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Safety notes
The default mode does not scan file contents; it only counts sensitive-looking environment files in Git status., Enable recursive git-secrets scanning only in repositories where you are authorized to inspect all files., Scanner mode invokes the git-secrets executable directly and does not fall back to Git aliases., Treat any scan warning as a stop-and-review signal before committing, sharing logs, or opening a PR.
Privacy notes
The default output prints counts only and does not print filenames or matched values., Recursive scans read repository files and may inspect sensitive local material., Terminal recordings can still reveal that a workspace contains sensitive environment files.
Author
MkDev11
Submitted by
MkDev11
Claim status
unclaimed
Last verified
2026-06-04

Decision playbook

Review trust signals before you adopt

Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.

Compare context
Selected

0

Current score

78

Baseline

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Complete

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done
  • Source provenance statusRequired

    Marked as source-backed.

    Done
  • Metadata reviewed

    Registry metadata indicates a reviewed listing.

    Done

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done
  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done
  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Needs review

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done
  • Package verification flag

    No package verification flag provided.

    Pending
  • Checksum metadata

    No checksum provided for downloaded artifact.

    Pending

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending
  • Baseline comparison available

    No baseline peer selected yet.

    Pending
  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

Config edit

Copy-ready — paste the snippet to get started.

Adoption plan

Balanced adoption plan

Current risk score 16/100. Use staged verification before broader rollout.

Risk 16

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done
  • Confirm metadata review state

    Listing has review metadata.

    Done
  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done
  • Review privacy notesRequired

    Privacy notes are present.

    Done
  • Verify package integrity metadata

    No package verification/checksum metadata.

    Pending

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending
  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending
  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Required evidence gates are covered (5/6 signals complete).

Risk 15

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Present

Review metadata is present.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required evidence gates are covered for this preset.

Decision timeline

Decision timeline · balanced

5/6 steps complete with no blocking gaps for this preset.

Risk 14

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is available.

Done

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

No required blockers for this timeline preset.

Prerequisite readiness

Prerequisite readiness

3 prerequisites to line up before setup.

0/3 ready
Install & runtime2General1

Safety & privacy surface

Safety & privacy surface

4 safety and 3 privacy notes across 3 risk areas. Review closely: credentials & tokens.

3 areas
  • SafetyLocal filesThe default mode does not scan file contents; it only counts sensitive-looking environment files in Git status.
  • SafetyCredentials & tokensEnable recursive git-secrets scanning only in repositories where you are authorized to inspect all files.
  • SafetyCredentials & tokensScanner mode invokes the git-secrets executable directly and does not fall back to Git aliases.
  • SafetyData retentionTreat any scan warning as a stop-and-review signal before committing, sharing logs, or opening a PR.
  • PrivacyLocal filesThe default output prints counts only and does not print filenames or matched values.
  • PrivacyLocal filesRecursive scans read repository files and may inspect sensitive local material.
  • PrivacyLocal filesTerminal recordings can still reveal that a workspace contains sensitive environment files.

Safety notes

  • The default mode does not scan file contents; it only counts sensitive-looking environment files in Git status.
  • Enable recursive git-secrets scanning only in repositories where you are authorized to inspect all files.
  • Scanner mode invokes the git-secrets executable directly and does not fall back to Git aliases.
  • Treat any scan warning as a stop-and-review signal before committing, sharing logs, or opening a PR.

Privacy notes

  • The default output prints counts only and does not print filenames or matched values.
  • Recursive scans read repository files and may inspect sensitive local material.
  • Terminal recordings can still reveal that a workspace contains sensitive environment files.

Prerequisites

  • Git installed and the command run from a repository worktree.
  • Optional git-secrets installed if GIT_SECRETS_STATUSLINE_SCAN is set to 1.
  • A slower refresh interval when optional scanning is enabled, because recursive scans can be expensive.

Schema details

Install type
config
Troubleshooting
No
Source repository stats
Scope
Source repo
Runtime and command metadata
Script language
bash
Script body
#!/usr/bin/env bash
set -u

main() {
if ! git rev-parse --is-inside-work-tree >/dev/null 2>&1; then
  echo "secrets: no repository"
  exit 0
fi

env_count=$(git status --porcelain=v1 -- .env '.env.*' .npmrc .pypirc .netrc 2>/dev/null | wc -l | tr -d ' ')

if [ "${GIT_SECRETS_STATUSLINE_SCAN:-0}" != "1" ]; then
  printf 'secrets: env files %s | scan opt-in\n' "$env_count"
  exit 0
fi

if command -v git-secrets >/dev/null 2>&1; then
  if git-secrets --scan -r . >/dev/null 2>&1; then
    printf 'secrets: env files %s | scan clean\n' "$env_count"
  else
    printf 'secrets: env files %s | review scan\n' "$env_count"
  fi
else
  printf 'secrets: env files %s | git-secrets missing\n' "$env_count"
fi
}

case $- in
  *n*) ;;
  *) main "$@" ;;
esac
Full copyable content
{
  "statusLine": {
    "type": "command",
    "command": "$CLAUDE_PROJECT_DIR/.claude/statuslines/git-secrets-env-risk-statusline.sh"
  }
}

About this resource

Source notes

  • AWS Labs git-secrets documents a Git-focused scanner for preventing secrets from being committed.
  • This entry focuses on local environment-file risk and optional git-secrets scanning rather than Gitleaks, which already has a dedicated tools entry.

Duplicate check

Checked existing statuslines, live HeyClaude statuslines, open pull requests, and repository content for git-secrets-env-risk-statusline, git-secrets, Gitleaks, sensitive environment statuslines, and secret-risk entries. The earlier Gitleaks submission was closed for matching content/tools/gitleaks.mdx; this replacement uses AWS Labs git-secrets with a different canonical source and scope.

Disclosure

Editorial statusline recipe. No paid placement or affiliate link is used.

Source citations

Add this badge to your README

Show that git-secrets Environment Risk Statusline is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/statuslines/git-secrets-env-risk-statusline.svg)](https://heyclau.de/entry/statuslines/git-secrets-env-risk-statusline)

How it compares

git-secrets Environment Risk Statusline side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

1 trust signal differ across this comparison (Submitter).

Next steps differ across entries — use the actions in the table below to copy install commands and source links per resource.

Field

Claude Code statusline that surfaces sensitive environment-file risk and can optionally run git-secrets as a local pre-commit-style scanner.

Open dossier

Claude Code statusline that shows the active kubectl context and namespace with a deployment-environment risk label.

Open dossier

Claude Code statusline that reads OSV-Scanner JSON results and prints a compact dependency vulnerability count for review sessions.

Open dossier

Claude Code statusline that summarizes MCP server count, remote endpoint count, and credential-surface hints without printing tokens, secrets, local paths, or full endpoint URLs.

Open dossier
Next stepsDiffers
Trust
Review statusReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewed
Package trustPackage not verifiedPackage not verifiedPackage not verifiedPackage not verified
Source provenanceSource-backedSource-backedSource-backedSource-backed
SubmitterDiffersMkDev11MkDev11MkDev11JSONbored
Install riskReview firstReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
BrandKubernetes logoKubernetes
Categorystatuslinesstatuslinesstatuslinesstatuslines
SourceSource-backedSource-backedSource-backedSource-backed
AuthorMkDev11MkDev11MkDev11JSONbored
Added2026-06-042026-06-042026-06-042026-06-05
Platforms
Harness
Source repo
Safety notesThe default mode does not scan file contents; it only counts sensitive-looking environment files in Git status. Enable recursive git-secrets scanning only in repositories where you are authorized to inspect all files. Scanner mode invokes the git-secrets executable directly and does not fall back to Git aliases. Treat any scan warning as a stop-and-review signal before committing, sharing logs, or opening a PR.The script is read-only and does not contact workloads, apply manifests, or change namespaces. The displayed context and namespace are limited to printable ASCII before terminal output. Risk labels are based on names; confirm the actual cluster and namespace before deployment commands. Avoid running write-capable automation solely because the statusline says an environment looks like development.Prefer reading a precomputed report; scanning dependencies during every statusline refresh can be slow. Auto-scan mode refuses symlinked report paths and writes through a temporary file before replacing the report. Vulnerability counts need human triage for reachability, exploitability, and acceptable remediation timing. Do not let a zero count replace lockfile review, provenance checks, or package-manager audit policy.This statusline is advisory and should not be used as the only MCP authorization review. It intentionally avoids printing full URLs, local paths, header names, tokens, or environment variable values. Remote endpoints and credential hints should trigger a separate review of protected resource metadata, scopes, and token handling.
Privacy notesThe default output prints counts only and does not print filenames or matched values. Recursive scans read repository files and may inspect sensitive local material. Terminal recordings can still reveal that a workspace contains sensitive environment files.Context and namespace names can expose customer, region, cluster, or service names in screenshots. kubectl reads local kubeconfig, which may reference private clusters and identities. The script does not print server URLs or certificates.OSV reports can reveal package names, versions, ecosystems, and repository structure. The statusline prints only the count, but the local JSON report may contain detailed dependency metadata. If scans run against private package manifests, review where the scanner sends package coordinates.The statusline reads Claude Code session metadata from stdin and prints only counts plus a generic credential hint. Avoid modifying the script to print full server URLs, headers, tokens, local config paths, or account identifiers on shared screens.
Prerequisites
  • Git installed and the command run from a repository worktree.
  • Optional git-secrets installed if GIT_SECRETS_STATUSLINE_SCAN is set to 1.
  • A slower refresh interval when optional scanning is enabled, because recursive scans can be expensive.
  • kubectl installed and configured for the environments you want visible.
  • A kubeconfig context selected before Claude Code starts or before the statusline refreshes.
  • Team naming conventions that distinguish production, staging, and development contexts.
  • OSV-Scanner JSON report at `osv-report.json`, or OSV_STATUSLINE_JSON set to another report path.
  • jq available for reading the report.
  • Optional OSV-Scanner CLI installed if OSV_STATUSLINE_SCAN is set to 1.
  • Claude Code CLI with statusline support.
  • jq installed locally.
  • MCP server metadata available in the Claude Code statusline input.
Install
mkdir -p .claude/statuslines
tmp="$(mktemp .claude/statuslines/mcp-auth-surface.sh.XXXXXX)"
cat > "$tmp" <<'EOF'
#!/usr/bin/env bash
set -u

input=$(cat)
if ! command -v jq >/dev/null 2>&1; then
  printf 'MCP auth: jq unavailable\n'
  exit 0
fi

servers=$(printf '%s' "$input" | jq -c '.mcp.servers // []' 2>/dev/null || printf '[]')
server_count=$(printf '%s' "$servers" | jq 'length' 2>/dev/null || printf '0')
remote_count=$(printf '%s' "$servers" | jq '[.[] | select((.url // .endpoint // "") | test("^https?://"))] | length' 2>/dev/null || printf '0')
credential_hint=$(printf '%s' "$servers" | jq '[.[] | select((.auth // .authorization // .headers // .env // null) != null)] | length' 2>/dev/null || printf '0')

if [ "$credential_hint" -gt 0 ]; then
  state="credentials: review"
else
  state="credentials: none shown"
fi

printf 'MCP auth: %s servers | %s remote | %s\n' "$server_count" "$remote_count" "$state"
EOF
chmod 700 "$tmp"
mv -f "$tmp" .claude/statuslines/mcp-auth-surface.sh
Config
{
  "statusLine": {
    "type": "command",
    "command": "$CLAUDE_PROJECT_DIR/.claude/statuslines/git-secrets-env-risk-statusline.sh"
  }
}
{
  "statusLine": {
    "type": "command",
    "command": "$CLAUDE_PROJECT_DIR/.claude/statuslines/kubectl-deployment-context-statusline.sh"
  }
}
{
  "statusLine": {
    "type": "command",
    "command": "$CLAUDE_PROJECT_DIR/.claude/statuslines/osv-dependency-risk-statusline.sh"
  }
}
{
  "statusLine": {
    "type": "command",
    "command": "$CLAUDE_PROJECT_DIR/.claude/statuslines/mcp-auth-surface.sh"
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Related guides

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.