We use Fallow for codebase intelligence on TypeScript and JavaScript projects—detecting dead code (unused files, exports, and dependencies), surfacing duplication before it spreads, and scoring complexity and health to prioritize refactoring.
Fallow runs as a CLI, a VS Code extension, and an MCP integration for coding agents, so the same analysis is available in CI, in the editor, and to AI assistants. An optional paid runtime-intelligence layer adds production hot/cold path data as evidence for safe deletions.
How We Use It
- Removing dead and cold code with confidence
- Catching duplication and complexity before it compounds
- Prioritizing refactoring with health scoring and runtime evidence
Monitoring & Testing
Why this matters: Observability and tests catch regressions early, reduce MTTR, and enable confident, frequent releases. We ship with confidence by instrumenting apps end-to-end: unit and integration tests, accessibility checks, and production observability. Our approach emphasizes fast feedback loops, clear failure signals, and actionable telemetry. Preferred defaults: Sentry for errors/perf, Playwright for E2E, Vitest or Bun Test for unit, OpenTelemetry for tracing, Lighthouse CI for budgets.