Skip to content
Fallow home
All docs pages

Docs home

Boundary violations

What a boundary-violation finding of fallow dead-code means, why it matters and how to fix it.

What it reports

Import crosses a configured architecture boundary.

Architecture explains how fallow finds it.

Why it matters

A module imports from a zone that its configured boundary rules do not allow. Boundary checks help keep layered architecture, feature slices, and package ownership rules enforceable.

Example

features/billing imports app/admin even though the configured boundary only allows imports from shared and entities.

Fix

Move the shared contract to an allowed zone, invert the dependency, or update the boundary config only if the architecture rule was wrong.

Facts

FactValue
Issue typeboundary-violation
Rule id in SARIF outputfallow/boundary-violation
Commandfallow dead-code
Default severityerror
Config key in rulesboundary-violation
Filter option--boundary-violations
Suppression comment// fallow-ignore-next-line boundary-violation
Fixable with fallow fixNo
Opt-inNo

Note. Requires configured boundary zones (boundaries config).

When to keep the code

  • A shared module that several zones need: change the boundary rules to allow these imports.
  • When you add boundaries to existing code, expect many findings. Start with the rule at warn.