codebase-churn — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited codebase-churn (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Generate a churn treemap from git history. Premise: files changed often (high commits) and heavily (high line churn) tend to harbor more bugs. Stable files are usually safer. Big + hot tiles are where to look first.
From the target repo:
python3 ~/.claude/skills/codebase-churn/scripts/churn_treemap.py \
-o churn-treemap.svg --report churn-report.mdOpen churn-treemap.svg in a browser. Hover any tile for path, commit count, lines added/deleted.
--report PATH) — ranked table of top files for tracking over time or pasting into a doc.| Tile | Meaning | Action |
|---|---|---|
| Big + red | Frequent and heavy edits | Refactor candidate. Likely under-tested. Bug-prone. |
| Big + blue | One large rewrite, then quiet | Probably stabilized. Verify it has tests. |
| Small + red | Many tiny touches (configs, version bumps) | Often a noisy interface or fragile contract. |
| Small + blue | Stable | Safe to leave alone. |
--since "6 months ago" — restrict the window. Defaults to all history.--until "2026-01-01" — pair with --since to compare windows.--top 100 — limit how many files appear (default 200).--exclude REGEX — repeatable. Lockfiles, node_modules/, dist/, *.min.* are excluded by default.--no-default-excludes — keep them in.-C path/to/repo — analyze a different repo than the cwd.paths... — restrict to subpaths (forwarded to git log -- ...).--since "3 months ago" and compare to the all-history view to spot newly-volatile areas.--report snapshots at intervals to track whether refactors actually lower churn.pip install.{old => new} collapses to the new path).- for their numstat).~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.