health

To check project health, run an audit that identifies known vulnerabilities, assesses dependency freshness, and reviews TODO backlogs. This generates a markdown health report with a structured summary, highlighting urgent fixes and low-risk improvements needed before release.

Documentation-to-code synchronization ensures your docs accurately reflect the current implementation. Auditing this alignment as part of a project health check prevents onboarding confusion, identifies stale documentation, and provides actionable cleanup guidance for maintenance workflows.

You can generate a report of accumulated TODOs and dependency vulnerabilities by running a comprehensive project health audit. It produces a markdown health report summarizing your TODO backlog and known security issues, optionally including repair prompts for remediation.

Yes, you can use a project health audit for large codebases during security reviews. It assesses dependency vulnerabilities and engineering hygiene across small to large projects, outputting a structured markdown summary that fits directly into kickoff or security review workflows.

The best way to get actionable remediation guidance for stale dependencies is by auditing project engineering health. It evaluates dependency freshness against known vulnerabilities and produces a markdown report with optional repair prompts to guide low-risk improvements.