eslint-plugin-boundaries
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:micromatch | AI (phantom-deps): micromatch is a direct runtime dep in package.json; phantom-dep heuristic is a false positive here. | ai | |
| phantom-deps | phantom-dep:eslint-import-resolver-node | AI (phantom-deps): eslint-import-resolver-node is a declared runtime dependency used via config/resolver indirection, not a direct import — stable false positive for this package. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 6.0.2 | 6 / 4 | |
| 5.4.0 | 5 / 4 | |
| 5.3.1 | 5 / 4 | |
| 5.3.0 | 5 / 2 | |
| 5.2.0 | 5 / 2 |
v6.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.