codebase-review

A codebase audit traces dependency graphs across packages to surface dead code and broken imports with cited file-path evidence. It generates a prioritized Markdown report per package to guide remediation in JavaScript or TypeScript monorepos.

A package-by-package codebase audit systematically reads all files to evaluate codebase health, identifying architectural inconsistencies and missing tests. It produces an evidence-backed Markdown report highlighting priorities and specific remediation steps per package.

Yes, you can run a codebase review on both monorepos and single-repo projects using JavaScript or TypeScript. The audit evaluates ongoing health, refactors, and onboarding reviews by tracing cross-package dependencies and citing file paths for every finding.

Yes, a dead code audit provides evidence for unused exports by reading all files and tracing dependency graphs across packages. Every finding cites specific file paths to ensure verifiable results and accurate architectural inconsistency detection.

The best way to prepare for a codebase refactor is to run a systematic health check that surfaces dead code, broken imports, and unstable workarounds. This generates a prioritized Markdown report with evidence-backed findings to guide your refactoring steps.