@yarn-tool/yarnlock
util for yarn.lock
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:@yarn-tool/table | AI (phantom-deps): Same-org monorepo dep; heuristic false positive for re-exported/indirect usage. | ai | |
| phantom-deps | phantom-dep:@yarnpkg/lockfile | AI (phantom-deps): Referenced in config/type files; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@yarn-tool/yarnlock-stringify | AI (phantom-deps): Same-org monorepo dep; heuristic false positive. | ai | |
| phantom-deps | phantom-dep:@yarn-tool/detect-yarnlock-version | AI (phantom-deps): Same-org monorepo dep; heuristic false positive. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 3.0.9 | 15 / 0 | |
| 3.0.8 | 15 / 0 | |
| 3.0.7 | 15 / 0 | |
| 3.0.5 | 15 / 0 | |
| 3.0.4 | 15 / 0 | |
| 3.0.3 | 15 / 0 |
v3.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.7
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. Consider requesting the maintainer enable provenance via CI/CD.
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.