health

To combine static analysis and test results into a code quality score, run your type checker, linter, test runner, dead code detector, and shell linter. The tool aggregates these outputs into a weighted 0-10 composite health score.

Tracking codebase health trends over time is done by recording the weighted 0-10 composite score from each health check invocation. This history surfaces continuous improvements and regressions rather than evaluating runs in isolation.

A dead code and shell lint detection health check works by invoking existing project tooling for each category. The tool aggregates linting and dead code detection results, applying a weighted calculation to generate an overall 0-10 code quality score.

You cannot use composite code quality scoring without existing tooling because it requires invoking your project's type checker, linter, test runner, dead code detector, and shell linter to compute the weighted 0-10 score.

Your codebase health score may be low because the 0-10 composite score is weighted across multiple checks. Failing static analysis, dead code detection, or shell linting issues will lower the overall score even if tests pass.

To run a full code health check and get a go/no-go quality signal, you need configured type checking, linting, test running, dead code detection, and shell linting tools. The tool executes these checks and returns a weighted composite score.