Added dependencies
What an added-dependency finding of fallow audit means, why it matters and how to fix it.
What it reports
The change adds a dependency.
Changed code explains how fallow finds it.
Why it matters
fallow audit reports a dependency that the change adds to a package.json. A new dependency is often correct, so the rule defaults to off. Set it to warn or error to review every new package. An invented package name already fails as an unresolved import or an unlisted dependency.
Example
A change adds "left-pad": "^1.3.0" to dependencies.
Fix
Check that the package exists, is maintained, and is not already covered by a dependency of the project. Suppress through overrides because package.json cannot hold a comment.
Facts
| Fact | Value |
|---|---|
| Issue type | added-dependency |
| Rule id in SARIF output | fallow/added-dependency |
| Command | fallow audit |
| Default severity | off |
Config key in rules | added-dependency |
Fixable with fallow fix | No |
| Opt-in | Yes |