@yarn-tool/yarnlock-entries
entries from yarnlock v1 and berry
10
Versions
ISC
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
bluelovers
Keywords
yarnyarn-toolnpmlernaworkspacespkgdependenciespackagespackage
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@yarn-tool/detect-yarnlock-version | AI (phantom-deps): Same-org scope dep declared in package.json; phantom-dep heuristic false positive for this monorepo package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 3.0.10 | 8 / 0 | |
| 3.0.9 | 8 / 0 | |
| 3.0.8 | 8 / 0 | |
| 3.0.6 | 8 / 0 | |
| 3.0.5 | 8 / 0 | |
| 3.0.4 | 8 / 0 | |
| 3.0.3 | 8 / 0 | |
| 3.0.2 | 8 / 0 | |
| 3.0.1 | 8 / 0 | |
| 3.0.0 | 8 / 0 |
v3.0.2
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.