health-check

Run a project health check weekly to execute drift checks, assess test coverage, perform security audits, and evaluate dependency freshness across multi-language stacks. This generates a consolidated health report for weekly reviews and pre-release readiness.

Dependency health evaluates package freshness and aging vulnerabilities, while drift detection identifies when project architecture diverges from its intended design state. Both are executed during a project health check to keep architectures aligned and dependencies updated.

Yes, you can apply this health check to pre-release checks and long-inactive periods. It evaluates test coverage across core, features, and adapters, surfacing security concerns and dependency health issues before generating a readiness report.

Assess test coverage gaps by executing the health check to scan core, features, adapters, and shared layers. This coverage assessment guides quality improvements by identifying untested areas within the multi-language stack.

The best way to surface security vulnerabilities and stale docs is running a consolidated health check. It performs security audits and checks for documentation drift, producing a unified report suitable for tracking project health over time.