Production safe to delete
What a runtime-safe-to-delete finding of fallow health means, why it matters and how to fix it.
What it reports
Statically unused and never invoked in production.
Runtime coverage explains how fallow finds it.
Why it matters
The function is both statically unreachable in the module graph and was never invoked during the observed runtime coverage window. This is the highest-confidence delete signal fallow emits.
Example
No module references formatLegacyInvoice in src/billing/legacy.ts, and the production capture shows no call to it.
Fix
Check that the capture window covers rare paths, such as a monthly job, then delete the function.
Facts
| Fact | Value |
|---|---|
| Issue type | runtime-safe-to-delete |
| Rule id in SARIF output | fallow/runtime-safe-to-delete |
| Command | fallow health |
Fixable with fallow fix | No |
Note. Requires --runtime-coverage input (V8 directory, V8 JSON, or Istanbul map).