Health Breakdown
The grade tells you how healthy the codebase is. The Health Breakdown tells you why.
It splits quality into five dimensions and colors each one green, amber, or red, so you can see at a glance which aspect is pulling the score down - and where your next improvement will have the most impact.
Maintainability
How easy the code is to understand and change. This is the dimension that most directly affects how fast your team can ship. Green means changes are safe and quick; red means even small edits are slow and risky.
Complexity
How tangled the logic is, on average. Complex code is harder to test, easier to break, and intimidating for new contributors. Red here is a strong signal that some code is doing too much and should be broken up.
Duplication
How much code is copy-pasted across the repository. Duplication multiplies maintenance - every fix has to be made in several places, and it’s easy to miss one. The breakdown also shows how many duplicate blocks were found.
Dead code
How much of the code is never used or can never run. Dead code adds noise, slows down onboarding, and can hide what the system actually does. The breakdown shows how many unused symbols were found, so you know how much is safe to delete.
Coupling
How interconnected the files are. When a file depends on too many others, it becomes hard to change in isolation and easy to break by accident. The breakdown highlights “hub” files that connect to an unusually large number of others - prime candidates for simplification.
Reading the colors
Across every dimension, the colors mean the same thing:
- Green - healthy. No action needed.
- Amber - worth watching. Fine for now, but trending toward trouble.
- Red - needs attention. This is where focused effort pays off most.
When you spot a red or amber dimension, switch to the Files explorer to find the specific files behind it.