merkle-patricia-tree
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Publish-env change on trusted ethereumjs package; no accompanying malicious behavior. | ai | |
| phantom-deps | phantom-dep:level-ws | AI (phantom-deps): level-ws is a declared runtime dep used indirectly; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/levelup | AI (phantom-deps): TypeScript types package loaded by convention; stable false positive for this package. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 4.2.4 | 6 / 17 | |
| 4.2.3 | 6 / 17 | |
| 4.2.2 | 7 / 17 | |
| 4.2.1 | 7 / 17 | |
| 4.2.0 | 7 / 22 | |
| 4.1.0 | 7 / 23 | |
| 4.0.0 | 7 / 21 |
v4.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (ralxz) than the most recent previously approved version (holgerd77) on 2021-10-06, but ralxz is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v4.2.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: holgerd77.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: holgerd77.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.