Code Health Badge
The badge at the top of the Health Overview answers one question fast: how healthy is this codebase overall?
It distills every file the scan analyzed into a single letter grade - from A (healthy) to F (critical) - with a 0–100 score next to it for a finer reading. Think of it like a credit score for your repository: one number that summarizes a lot of underlying detail, handy for spotting trends and comparing repositories side by side.
What each grade means
| Grade | Label | What it tells you |
|---|---|---|
| A | Healthy | Easy to work in. New contributors get up to speed quickly. |
| B | Good | Solid overall, with a few files worth keeping an eye on. |
| C | Moderate | Workable, but friction is building up in places. |
| D | At risk | Changes are getting slow and risky. Time to invest. |
| F | Critical | The codebase is actively holding the team back. |
The score next to the grade moves on the same scale, so you can track small improvements from one scan to the next even before the letter changes.
The numbers behind the grade
Four tiles sit alongside the badge to give it context at a glance.
Files analyzed
How many source files the scan successfully read and scored. This is the population every other number is based on.
Avg. maintainability
The typical “how easy is this to change” score across the whole repository - the main driver behind the grade.
High-risk files
How many files carry enough risk to deserve attention soon, shown as both a count and a share of the codebase. These are the files most likely to cause bugs or slow you down - see Risk score.
Lines of code
The overall size of the codebase - a quick sense of scale. It doesn’t affect the grade on its own.