health

You can aggregate code quality metrics into a single health score by running type checks, linting, tests, and dead-code detection, which generates a weighted 0-10 score for your repository.

Tracking code quality trends over time is done by computing a weighted health score from multiple linters and test runners, then persisting these metrics per commit to visualize regressions.

Yes, you can detect code regressions by monitoring the weighted 0-10 health score, which orchestrates type checks and dead-code detection to flag drops in quality across commits.

This code health monitoring approach works directly with type checkers, test runners, linters, and dead code detectors to compute a unified health score for your software repository.

You visualize code quality trends to prioritize fixes via a dashboard by running a health check that aggregates type checking and linting results, persisting the weighted score per commit.

You need a unified code health score when individual linter outputs become hard to gauge, allowing you to monitor overall repo health and track regressions over time using a single metric.