How healthy is our codebase?

Questions CTOs ask

How do you measure codebase health?

This tool rates eight dimensions — code quality, testing, documentation, architecture, dependencies, performance, deployment and monitoring — each from five weighted statements you score yourself 1 to 5. It reports a grade per dimension and the weakest statements to fix first. It does not scan your repository: nothing here computes cyclomatic complexity, reads a coverage report or looks up CVEs, so the output is only as honest as the answers. That is a feature for a first pass — it surfaces where the team disagrees — but pair it with real tooling before you put a number in front of a board.

What is a good test coverage percentage?

The optimal test coverage target depends on the criticality of the system. For most business applications, 70-80% line coverage with meaningful assertions (not just exercising code paths) provides a strong safety net. Critical systems (payments, healthcare, security) should target 85-95%. Below 60%, teams typically lack confidence to refactor safely. Above 90%, returns diminish rapidly and maintenance cost of tests themselves becomes significant. Focus on covering critical paths and business logic rather than chasing a number.