About Fallow

I spent most of my career as a frontend developer and tech lead. The bugs that cost me the most were never in one file. They were disagreements between files that never mention each other: two route segments named [id] and [slug] at the same level, an inject with no provider anywhere in the tree, a formatDate and a dateFormat written eighteen months apart by two people who never met.

The linter checks the file. TypeScript checks the types. The tests check what someone thought to describe. Nothing checks the codebase as a whole, so I built the tool that does. Fallow reads the whole module graph in under a second, which is fast enough for a pre-commit hook, so a finding arrives while the change is still in your head.

Coding agents made this more urgent. An agent sees a large repository through a keyhole, so it will happily write a fourth date formatter without knowing about the other three. Fallow gives the agent, and you, the view of the whole repository.

Fallow is bootstrapped. There are no investors and no venture capital, so I decide where Fallow goes, and the people I answer to are the people who use it. The analyzer stays free and open source under the MIT license. Sponsorship and grants pay for maintenance time, so the project can keep a steady release cycle.

The source of the free scan is public at github.com/fallow-rs/fallow, with every release, every release note and the issue tracker. The documentation is public too, in fallow-rs/docs. When Fallow reports something, you can read the code that decided it.

Early on, Fallow ran in a checkout without node_modules and concluded, with great confidence, that nearly everything was dead. Our own CI caught it. Since then every verdict carries a confidence level, because an analyzer that cannot say “I’m not sure” is not one you should delete code on.

The scan runs locally. It reads your files and writes a report, and it uploads no source code. Product telemetry is off until you turn it on. The telemetry page lists each field it would send, and the privacy policy covers this website.

• Legal name: Fallow B.V.
• Registration: Dutch Chamber of Commerce (KVK) number 42095869
• Founded: 2026, in the Netherlands
• Email: hello@fallow.tools. The contact page tells you what to send where.
• LinkedIn: Fallow on LinkedIn