Fallow documentation
Find the code you can delete, merge, or refactor in a TypeScript or JavaScript project. Fallow analyzes code and styles statically for free, and Fallow Cloud, the optional paid product, shows what ran in production.
Fallow shows you which code in a TypeScript or JavaScript project you can delete, merge, or refactor. It is codebase intelligence: one command reads your whole module graph and reports what it finds.
The static layer finds:
- unused code
- duplication
- complexity hotspots
- architecture drift
- styling drift from your design system
- feature-flag branches
To learn which code executed in production, add the optional runtime layer.
Start here
Run fallow without installing
npx fallowThe first run needs no config.
Read the results
One pass reports dead code, duplication, and complexity. For styling drift, run
fallow auditorfallow health --css.Go deeper
npx fallow dead-code npx fallow dupes npx fallow health npx fallow fix --dry-run
What fallow helps you do
Find unused files, exports, and dependencies, and remove them.
Find repeated logic before it spreads.
Rank code by complexity and health, and fix the worst first.
Confirm exact symbol use, class contracts, affected files, and the tests to run.
See hot paths and cold paths, and back a delete with production data.
Pick your workflow
Start here. The CLI runs locally, in CI, and in agent loops.
Get real-time diagnostics, Code Lens, and one-click fixes in the editor.
Give Claude Code, Cursor, and other agents structured tool calls.
Understand the two layers
Static analysis tells you which code is connected to which. Production data from Fallow Cloud tells you which code actually ran. fallow health shows both.
Learn how the two layers differ before you set up runtime collection.