GLOSSARY

What Is a Codebase Health Score?

A codebase health score is a single number, usually from 0 to 100, that summarises the maintainability of a repository by combining several measured signals — such as dead code, test coverage, file size and duplication — into one figure you can track over time.

What goes into one

A health score starts at a maximum and deducts for measured problems: unused code, low test coverage, oversized files, duplication, exposed secrets, and unreachable clusters. Each deduction is usually capped so no single dimension can sink the whole score.

The value of a single number is that it is trendable and can be communicated to people who do not read code — a direction of travel that a non-engineer can follow release to release.

Its limits

A score is a summary, not a diagnosis. Two repositories with the same score can have very different problems, so the per-dimension breakdown is where the actionable information is.

It is most useful as a relative measure — this repo against itself over time, or against a team baseline — rather than as an absolute grade.

Common questions

What is a codebase health score?

It is a single number, usually 0 to 100, that combines measured maintainability signals — dead code, coverage, file size, duplication and more — into one figure you can track over time.

How is codebase health measured?

By starting from a maximum score and applying capped deductions for each measured problem in the repository, then summing the result into one number with a visible per-dimension breakdown.

What is a good code health score?

There is no universal threshold. The score is most meaningful tracked against the same repository over time or against a team baseline, rather than read as an absolute grade.

Related

See it in your own codebase.

Analyze my codebase →

No credit card required · Free tier available