Refactoring target
What a refactoring-target finding of fallow health means, why it matters and how to fix it.
What it reports
File identified as a high-priority refactoring candidate.
Health explains how fallow finds it.
Why it matters
File identified as a refactoring candidate based on a weighted combination of complexity density, churn velocity, dead code ratio, fan-in (blast radius), and fan-out (coupling). Categories: urgent churn+complexity, break circular dependency, split high-impact file, remove dead code, extract complex functions, reduce coupling.
Example
A file combines high complexity density, churn, fan-in, and dead-code signals.
Fix
Start with the listed evidence: remove dead exports, extract complex functions, then reduce fan-out or cycles in small steps.
Facts
| Fact | Value |
|---|---|
| Issue type | refactoring-target |
| Rule id in SARIF output | fallow/refactoring-target |
| Command | fallow health |
| Filter option | --targets |
Fixable with fallow fix | No |