Explanations
Understand why fallow reports what it reports, so you can trust a finding and act on it. Covers static analysis vs production data, fallow vs linters, health, duplication, and dead code.
These pages explain why fallow reports what it reports. Read them when you want to know if you can trust a finding, or which analysis fits your problem.
Static analysis shows what is connected. Runtime data shows what actually ran.
What a project-wide analysis finds that a file-local tool cannot.
How fallow computes the health score, maintainability, and refactor targets.
The four detection modes and when to use each.
What fallow counts as reachable, and why.
What opt-in telemetry sends, and how to inspect it first.
If you are new to fallow, start with Static analysis vs production data and Fallow vs linters.