Claude Code statusline that uses simple-git status data to show dirty worktree risk, staged changes, untracked files, and merge conflicts.
Open the source and read safety notes before installing.
Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.
Decision playbook
Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.
0
78
—
No baseline selected
No major trust-signal divergence detected in the current selection.
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Source provenance statusRequired
Marked as source-backed.
Metadata reviewed
Registry metadata indicates a reviewed listing.
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Trust level risk gateRequired
Trust level does not block evaluation.
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Package verification flag
No package verification flag provided.
Checksum metadata
No checksum provided for downloaded artifact.
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
Baseline comparison available
No baseline peer selected yet.
Diverging trust signals identified
No major trust-signal divergence found.
Setup at a glance
Copy-ready — paste the snippet to get started.
Adoption plan
Current risk score 16/100. Use staged verification before broader rollout.
Validate source and review signals before any execution.
Confirm source provenanceRequired
Source URL/provenance metadata is present.
Confirm metadata review state
Listing has review metadata.
Verify install payload
Install/config payload exists and can be inspected.
Confirm safety, privacy, and package integrity signals.
Review safety notesRequired
Safety notes are present.
Review privacy notesRequired
Privacy notes are present.
Verify package integrity metadata
No package verification/checksum metadata.
Adopt in controlled steps based on the selected plan.
Run in isolated sandbox firstRequired
Use a constrained sandbox and observe behavior across multiple tasks.
Roll out graduallyRequired
Roll out to a small cohort before wider usage.
Set monitoring and fallback
Define rollback path and monitor errors after adoption.
Evidence readiness
Required evidence gates are covered (5/6 signals complete).
Source repository/provenance is listed.
Required in this preset
Review metadata is present.
Required in this preset
Safety notes are present.
Required in this preset
Privacy notes are present.
Optional in this preset
Package integrity metadata is missing.
Optional in this preset
Install payload is available.
Required in this preset
Required evidence gates are covered for this preset.
Decision timeline
5/6 steps complete with no blocking gaps for this preset.
triage
Source/provenance metadata is available.
triage
Review metadata is available.
verify
Safety notes are available.
verify
Privacy notes are available.
verify
Package integrity metadata is missing.
rollout
Install payload is available.
No required blockers for this timeline preset.
Prerequisite readiness
3 prerequisites to line up before setup.
Safety & privacy surface
3 safety and 3 privacy notes across 3 risk areas.
#!/usr/bin/env node
let simpleGit;
try {
simpleGit = require("simple-git");
} catch {
console.log("worktree: simple-git missing");
process.exit(0);
}
async function main() {
const git = simpleGit({ baseDir: process.cwd(), maxConcurrentProcesses: 1 });
const isRepo = await git.checkIsRepo();
if (!isRepo) {
console.log("worktree: no repository");
return;
}
const status = await git.status();
const branch = status.current || "detached";
const staged = (status.staged || []).length;
const dirty =
(status.modified || []).length +
(status.deleted || []).length +
(status.renamed || []).length;
const untracked = (status.not_added || []).length + (status.created || []).length;
const conflicts = (status.conflicted || []).length;
let risk = "clean";
if (conflicts > 0) {
risk = "blocked";
} else if (staged > 0 && dirty > 0) {
risk = "split";
} else if (dirty + untracked > 10 || staged > 20) {
risk = "high";
} else if (dirty > 0 || untracked > 0) {
risk = "watch";
} else if (staged > 0) {
risk = "review";
}
console.log(
`worktree: ${branch} | risk ${risk} | staged ${staged} | dirty ${dirty} | untracked ${untracked} | conflicts ${conflicts}`,
);
}
main().catch(() => {
console.log("worktree: unavailable");
});{
"statusLine": {
"type": "command",
"command": "node $CLAUDE_PROJECT_DIR/.claude/statuslines/simple-git-worktree-risk-statusline.cjs"
}
}git.status().Checked existing statuslines, live HeyClaude statuslines, open pull requests, and repository content for simple-git-worktree-risk-statusline, simple-git, dirty worktree, Git status statusline, and worktree risk. The earlier git-worktree-risk-statusline submission was closed because it reused the Git status manual and git-scm.com; this replacement uses simple-git with a different canonical source, runtime, slug, and value proposition.
Editorial statusline recipe. No paid placement or affiliate link is used.
Show that simple-git Worktree 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/simple-git-worktree-risk-statusline)simple-git Worktree Risk Statusline side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
| Field | Claude Code statusline that uses simple-git status data to show dirty worktree risk, staged changes, untracked files, and merge conflicts. Open dossier | Claude Code statusline that uses git-machete branch layout data to show whether the current branch is managed, how many branches are outside the layout, and when fork-point overrides need review. Open dossier | 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 reads OSV-Scanner JSON results and prints a compact dependency vulnerability count for review sessions. Open dossier |
|---|---|---|---|---|
| Next steps | ||||
| Trust | ||||
| Review status | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed |
| Package trust | Package not verified | Package not verified | Package not verified | Package not verified |
| Source provenance | Source-backed | Source-backed | Source-backed | Source-backed |
| Submitter | MkDev11 | MkDev11 | MkDev11 | MkDev11 |
| Install risk | Review first | Review first | Review first | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Brand | — | — | — | — |
| Category | statuslines | statuslines | statuslines | statuslines |
| Source | Source-backed | Source-backed | Source-backed | Source-backed |
| Author | MkDev11 | MkDev11 | MkDev11 | MkDev11 |
| Added | 2026-06-04 | 2026-06-04 | 2026-06-04 | 2026-06-04 |
| Platforms | ||||
| Harness | ||||
| Source repo | — | — | — | — |
| Safety notes | ✓This is a read-only review aid; inspect the actual diff before committing, rebasing, merging, or discarding files. Frequent statusline refreshes can still run Git status often in large repositories, so use a moderate refresh interval. Treat split staged/dirty state and conflict counts as stop-and-review cues before automated edits. | ✓This statusline is read-only and does not run git-machete update, traverse, rebase, push, or pull. Unmanaged branches and fork-point overrides are review cues; inspect git-machete status before changing stacked branches. The compact output intentionally avoids automated branch repair because stacked-branch workflows can rewrite history. | ✓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. | ✓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. |
| Privacy notes | ✓The statusline prints aggregate counts and the branch name, not file paths, diff hunks, or commit messages. Branch names can reveal ticket IDs, customer names, incident labels, or release names in screenshots. The simple-git library shells out to local Git; any custom Git wrappers or hooks are outside this script's control. | ✓The script prints the current branch name and aggregate branch-layout counts. Branch names can reveal ticket IDs, customers, incidents, or release names in terminal screenshots. It reads local branch layout metadata and does not print commit messages, remote URLs, or file paths. | ✓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. | ✓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. |
| Prerequisites |
|
|
|
|
| Install | — | — | — | — |
| Config | | | | |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Source-backed guides for putting this to work.
Map Claude Code sandbox environments to team risk boundaries.
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.