Boundary coverage
What a boundary-coverage finding of fallow dead-code means, why it matters and how to fix it.
What it reports
Source file matches no configured architecture boundary zone.
Architecture explains how fallow finds it.
Why it matters
A file outside every zone is outside every boundary rule, so it can import from any layer. New code in that file can break the architecture, and no check reports it.
Example
src/generated/client.ts is reachable but does not match any boundaries.zones[].patterns entry.
Fix
Add the file to the intended zone pattern, move it under a zoned directory, or add a generated-file glob to boundaries.coverage.allowUnmatched.
Facts
| Fact | Value |
|---|---|
| Issue type | boundary-coverage |
| Rule id in SARIF output | fallow/boundary-coverage |
| Command | fallow dead-code |
| Default severity | error |
Config key in rules | boundary-violation |
| Filter option | --boundary-violations |
| Suppression comment | // fallow-ignore-file boundary-violation |
Fixable with fallow fix | No |
| Opt-in | No |
Note. Requires boundaries.coverage.requireAllFiles.