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.
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.
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.
[](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.
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.
✓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.
✓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 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.
✓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.