@nori-zk/proof-conversion
Verifying zkVM proofs inside o1js circuits, to generate Mina compatible proof
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@nori-zk/proof-conversion-pairing-utils | AI (dependencies): Sibling package from same maintainer/org. | ai | |
| source-diff | encoded-string-file:build/src/groth/risc0/decode_tx.js | AI (source-diff): Hex test fixture for tx decoding, not an obfuscated payload. | ai | |
| source-diff | encoded-string-file:build/src/plonk/piop/e2e_playground.js | AI (source-diff): Hex proof fixture used in e2e test/playground script. | ai | |
| source-diff | encoded-string-file:build/src/plonk/piop/e2e_test.js | AI (source-diff): Hex proof fixture for PIOP verifier e2e test. | ai | |
| source-diff | encoded-string-file:build/src/plonk/e2e_test.js | AI (source-diff): Hex-encoded zk proof fixture used in e2e test, not a hidden payload. | ai | |
| phantom-deps | phantom-dep:bytebuffer | AI (phantom-deps): Used indirectly via config/build tooling, common false positive. | ai | |
| phantom-deps | phantom-dep:typescript | AI (phantom-deps): TypeScript is a build dep referenced via tsconfig, not direct import. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all 19 versions; absence of provenance is common and not a risk signal for this package. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 0.8.26 | 4 / 12 | |
| 0.8.25 | 4 / 12 | |
| 0.8.24 | 4 / 12 | |
| 0.8.23 | 4 / 12 | |
| 0.8.22 | 4 / 12 | |
| 0.8.21 | 4 / 12 | |
| 0.8.20 | 4 / 12 | |
| 0.8.19 | 4 / 12 | |
| 0.8.18 | 4 / 12 | |
| 0.8.17 | 4 / 12 | |
| 0.8.16 | 4 / 12 | |
| 0.5.10 | 7 / 13 | |
| 0.5.9 | 7 / 13 | |
| 0.5.8 | 7 / 10 | |
| 0.5.6 | 7 / 10 | |
| 0.5.3 | 7 / 10 | |
| 0.1.3 | 4 / 10 | |
| 0.1.2 | 4 / 10 | |
| 0.1.1 | 4 / 10 |
v0.8.26
2 findingsModified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.25
2 findingsModified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.24
2 findingsModified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.10
4 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.9
5 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (kirol) than the most recent previously approved version (jk89) on 2025-06-23, but kirol 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.
v0.5.8
5 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.6
2 findingsModified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
2 findingsModified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.