CODEBASE HEALTH SCORE
One codebase health score, from 0 to 100, for the state of your code.
The Health Score starts at 100 and deducts across six measured dimensions — dead code, zombie code, file size, test coverage, secrets exposure and duplication. Every deduction is capped, so no single problem sinks the whole score, and every point is shown.
A codebase health metric built from six measured dimensions
A summary, not another scan
The score reflects scans you have already run. Nothing is hidden in a black box — the breakdown shows exactly where each point went.
The tile and the tab never disagree
Dead code and zombie deductions count only findings you can see on the tab — a dismissed flag is excluded from both.
Tracks cleanups over time
With Autopilot on, a cleanup shows up in the score the morning after it merges, so the number stays honest.
See your Health Score in under 2 minutes.
Analyze my codebase →No credit card required · Free tier available
Common questions
How is the codebase health score calculated?
It starts at 100 and applies capped deductions across six measured dimensions: dead code, zombie code, file size, test coverage, secrets exposure and duplication. Every deduction is shown.
What is a good codebase health score?
There is no universal threshold. The score is most useful tracked against the same repository over time, or against a team baseline, rather than read as an absolute grade.
What are the six dimensions the score measures?
Dead code, zombie code, oversized files, test coverage, exposed secrets and code duplication.