@yarn-tool/node-modules-link
link package to node_modules
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:fs-extra | AI (phantom-deps): fs-extra is a declared dependency used transitively; phantom-dep heuristic fires on config references, not a real risk. | ai | |
| phantom-deps | phantom-dep:@ts-type/package-dts | AI (phantom-deps): Type-only package declared as dep; phantom-dep fires on config references, stable false positive for this package. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 3.0.11 | 9 / 0 | |
| 3.0.10 | 9 / 0 | |
| 3.0.9 | 9 / 0 | |
| 3.0.8 | 9 / 0 | |
| 3.0.5 | 9 / 0 | |
| 3.0.4 | 9 / 0 | |
| 3.0.3 | 9 / 0 |
v3.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.