Code Health
Every codebase carries hidden cost: the files everyone is afraid to touch, the functions that take an afternoon to understand, the modules where bugs keep coming back. Code Health makes that cost visible.
On every scan, it reads the structure of your repository and turns it into a clear, repository-wide read on quality - so you can answer the questions that usually come down to a senior engineer’s gut feel:
- Is this codebase easy or painful to work in?
- Which files are slowing the team down?
- Are we getting better or worse over time?
There’s nothing to set up. No agents, no code changes. Code Health is calculated automatically as part of the same scan that runs your security checks, and it always reflects the exact commit that was scanned.
Where to find it
Open any repository’s Security report and select the Code Metrics tab.
Two ways to read it
Health Overview
The big-picture view. A single health grade for the whole repository, the headline numbers behind it, and a five-part breakdown that shows which aspect of quality needs attention. Start here to see how the codebase is doing at a glance.
Files explorer
The drill-down view. A list of files ranked by how much risk they carry, with the riskiest surfaced first. Open any file to see its scores, its size and dependencies, and the functions most in need of attention. Use this when you want to know what to fix first.
Always current
Code Health is recalculated from scratch on every scan - whether you trigger it from the dashboard, the CLI, or your CI/CD pipeline. There’s nothing to keep in sync: the numbers always match the latest scanned commit, which makes Code Health a dependable way to track quality trends release over release.