code-health — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited code-health (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.
Repowise scores every file 1–10 from deterministic biomarkers — McCabe complexity, deep nesting, brain methods, class cohesion (LCOM4), god classes, clone detection, untested hotspots, function-level churn, ownership dispersion, and more. Zero LLM calls; pure local analysis. The weights are calibrated against a real defect corpus, so a low score means more likely to harbour bugs, not just bigger.
get_health() (no targets): repo-level KPIs plus thelowest-scoring files. Start here for "how healthy is this codebase?" or "what should we clean up?".
get_health(targets=["src/x.py", "src/y.py"]): per-file scoreand the specific biomarker findings driving it. Use before/after a refactor, or to explain why a file is flagged.
include flagsget_health(targets=[...], include=[...]):
"biomarkers" — always return the findings list (what's wrong, where)."refactoring" — deterministic, ranked refactoring suggestions (by impact/effort)."coverage" — surface coverage data when it's been ingested."trend" — recent health snapshots + declining / predicted-decline signal.get_health(targets=[worst files], include=["refactoring"]) and present the ranked suggestions, not just the scores.
what each one means in plain language. Avoid dumping the raw payload.
get_risk(targets=[...]); a filethat is both low-health and a churn hotspot deserves the most care.
light up once they ingest a report: repowise health --coverage cov.lcov (LCOV / Cobertura / Clover).
repowise health — KPIs + lowest-scoring filesrepowise health --refactoring-targets — ranked by impact / effortrepowise health --trend — snapshots + declining alertsrepowise health --coverage <file> — ingest coverage, light up untested-hotspotIf get_health reports no repository, suggest /repowise:init. Code health is computed even in index-only mode (no LLM needed), so it should be available whenever the repo is indexed.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.