audit

To run a comprehensive codebase audit, execute a single command to analyze security, performance, accessibility, SEO, dependency hygiene, and dead code. The audit synthesizes these checks into a prioritized markdown punch list for immediate repository rehabilitation.

Detecting framework drift and outdated dependencies involves analyzing your project against expected conventions and running stack dependency audits. This process flags version mismatches and stale packages, adding them to a prioritized rehab list.

Pre-deploy validation uses tools like detect-secrets and npm audit to scan for exposed credentials and vulnerable packages. It checks dependency hygiene by identifying outdated libraries and potential security risks before release.

You can check DESIGN.md token compliance by comparing documented design tokens against actual code usage. This spec compliance audit identifies drift between intended design architecture and implemented frontend components.

Dead code detection relies on static analysis tools like ts-prune and depcheck, which may miss dynamically imported modules or complex runtime references. It works best on structured codebases with expected CI conventions.

Yes, generating a repository rehab punch list requires jq and npm audit installed to parse JSON outputs and analyze dependency vulnerabilities. These dependencies enable the structured analysis of security and hygiene metrics.