Track health
Read the health score, factors, engineering signals, and trends.
See where maintenance cost concentrates — and whether it is getting worse.
prism health
prism health --verbose
prism health --json | jq '.data.score'
prism engineering
prism engineering --fail-on highWhat you get back
Health score (0–100, higher better) from five factors: parse health, test presence, coupling, modularity, diagnostics. The factors matter more than the letter grade.
Engineering report — entropy, drift, debt, churn, hotspots (high churn × high complexity).
Trends — snapshots keyed by commit; early points may be git-backfilled and marked estimated. See signal provenance.
When this is wrong
- Not a code-quality or correctness score — structural heuristics only.
- Not comparable across repositories; compare a repo to its own past.
- Unavailable coverage/churn is absence, not zero — do not treat missing as green.