Unused catalog entries
What an unused-catalog-entry finding of fallow dead-code means, why it matters and how to fix it.
What it reports
Catalog entry not referenced by any workspace package.
Dependencies explains how fallow finds it.
Why it matters
No package uses the pinned version, but the entry still gets version updates and reviews. Readers assume that some workspace depends on it.
Example
The catalog source declares catalog: { is-even: ^1.0.0 }, but no workspace package.json declares "is-even": "catalog:".
Fix
Delete the entry from the catalog source file. If any consumer uses a hardcoded version (surfaced in hardcoded_consumers), switch that consumer to catalog: first to keep versions aligned.
Facts
| Fact | Value |
|---|---|
| Issue type | unused-catalog-entry |
| Rule id in SARIF output | fallow/unused-catalog-entry |
| Command | fallow dead-code |
| Default severity | warn |
Config key in rules | unused-catalog-entries |
| Filter option | --unused-catalog-entries |
Fixable with fallow fix | Yes |
| Opt-in | No |
When to keep the code
- When a workspace pattern names a directory that does not exist yet, for example a repository that CI clones there, fallow does not report catalog entries. Packages in that directory can use them.