[rocket]Getting Started

  • index
  • installation
  • quickstart
  • adoption

[magnifying-glass]Analysis

  • index
  • dead code
  • type aware
  • duplication
  • similar code
  • boundaries
  • auto fix
  • runtime coverage
  • production mode
  • file types
  • css analysis
  • debugging
  • limitations

[cloud]Cloud

  • beacon

[gear]Configuration

  • overview
  • rules
  • suppression
  • workspaces
  • boundaries
  • environment

[plug]Integrations

  • index
  • mcp
  • node bindings
  • agent skills
  • claude hooks
  • vscode
  • neovim
  • ci
  • badges

[book-open]Explanations

  • index
  • static vs runtime
  • fallow vs linters
  • health
  • duplication
  • dead code
  • telemetry

[puzzle-piece]Frameworks

  • react
  • built in
  • custom plugins

[right-left]Migration

  • comparison
  • from knip
  • from jscpd

Explanations

These pages explain the model behind the tool.

[chart-network]Static vs runtime intelligence

Static answers "what is connected". Runtime answers "what actually ran".

[scale-balanced]Fallow vs linters

Why project-wide analysis catches what file-local tools cannot.

[heart-pulse]Health explained

How health, maintainability, and refactor targets are computed.

[clone]Duplication explained

The four detection modes and when to use each.

[skull-crossbones]Dead code explained

What Fallow considers reachable and why.

If you are new to Fallow, start with Static vs runtime intelligence and Fallow vs linters.