@nori-zk/ethprocessor
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 |
|---|---|---|---|---|
| npm-metadata | url-dep:o1js | AI (npm-metadata): URL points to a specific commit of the official o1-labs/o1js repo via pkg.pr.new; consistent pattern for this ZK package pinning pre-release builds. | ai | |
| phantom-deps | phantom-dep:mina-attestations | AI (phantom-deps): mina-attestations is a declared runtime dep; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 6.0.6 | 6 / 17 | |
| 6.0.5 | 6 / 17 | |
| 6.0.4 | 6 / 17 | |
| 6.0.3 | 4 / 16 | |
| 6.0.2 | 4 / 16 | |
| 6.0.1 | 4 / 16 | |
| 6.0.0 | 4 / 16 |
v6.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.