health

Code quality trends are tracked by computing a weighted 0-10 health score from standard project tools across commits and releases. This score combines a type checker, linter, test runner, dead code detector, and shell linter to visualize regressions or improvements over time.

Yes, you can integrate static analysis and lint checks into a single CI health score by combining a type checker, linter, test runner, dead code detector, and shell linter. This produces a weighted 0-10 metric ready for CI/CD pipeline integration.

A weighted code health score is a single 0-10 metric that combines results from a type checker, linter, test runner, dead code detector, and shell linter. It wraps these isolated project tools to provide an interpretable assessment of codebase quality.

Yes, the code health dashboard computes a weighted 0-10 score and applies it to codebases of various sizes. It monitors quality trends over time and generates CI-ready insights to guide maintenance and process improvements.

To generate a code health report, run the health command to compute a weighted 0-10 score from your project's type checker, linter, test runner, dead code detector, and shell linter. This outputs a trend report for your codebase.

Combining dead code detection and test runners into one quality metric prevents isolated checks from hiding overall degradation. The weighted 0-10 health score provides an interpretable view of codebase quality and guides CI/CD improvements.