Run npx fallow audit in any TypeScript or JavaScript repository. Fallow builds a deterministic dependency graph, then reports unused code, cycles, duplicated logic, complexity, and architecture drift. Its changed-code gate blocks only findings introduced by the current change, so existing debt does not stop adoption. Use the same evidence locally, in CI, editors, and MCP workflows. The analyzer is free and MIT licensed; optional Fallow Runtime adds production execution evidence.

The first command I want people to run is npx fallow audit. It maps the repository before judging the change, because the risk in a larger TypeScript codebase often sits outside the file you are editing. I chose deterministic evidence as the foundation because the same code should produce the same finding twice, especially when CI can block a merge. Stable fingerprints and typed JSON give every integration one result to work from. Many existing repositories already have years of debt. The default changed-code gate fails only on findings introduced by the current change, so you can start using Fallow without turning that backlog into an all-or-nothing cleanup project. If the first run misreads your repository or its framework conventions, that is the feedback I want most.

Fallow

Codebase intelligence for TypeScript and JavaScript

Codebase intelligence for TypeScript and JavaScript