@provablehq/sdk
A Software Development Kit (SDK) for Zero-Knowledge Transactions
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:xmlhttprequest-ssl | AI (phantom-deps): Config-referenced HTTP polyfill, benign. | ai | |
| phantom-deps | phantom-dep:core-js | AI (phantom-deps): Known implicit polyfill dependency. | ai | |
| phantom-deps | phantom-dep:sync-request | AI (phantom-deps): Config-referenced, standard for node build target. | ai | |
| phantom-deps | phantom-dep:@provablehq/wasm | AI (phantom-deps): Same-org WASM binding, expected pattern. | ai | |
| phantom-deps | phantom-dep:mime | AI (phantom-deps): Config-referenced, not a real risk for this SDK bundler setup. | ai | |
| provenance | publisher-changed | AI (provenance): Legitimate org maintainer transition, no behavioral change in package. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Same transition; publisher has track record with approved packages. | ai | |
| phantom-deps | phantom-dep:comlink | AI (phantom-deps): comlink is a declared runtime dep used in worker/browser bundling context; phantom-dep false positive for this package. | ai |
Versions (showing 49 of 49)
| Version | Deps | Published |
|---|---|---|
| 0.11.4 | 7 / 25 | |
| 0.11.3 | 7 / 25 | |
| 0.11.2 | 7 / 25 | |
| 0.11.1 | 7 / 25 | |
| 0.11.0 | 7 / 25 | |
| 0.10.5 | 7 / 25 | |
| 0.10.4 | 7 / 25 | |
| 0.10.3 | 7 / 25 | |
| 0.10.2 | 7 / 23 | |
| 0.10.1 | 7 / 23 | |
| 0.10.0 | 7 / 23 | |
| 0.9.18 | 7 / 23 | |
| 0.9.17 | 7 / 23 | |
| 0.9.16 | 7 / 23 | |
| 0.9.15 | 6 / 23 | |
| 0.9.14 | 7 / 23 | |
| 0.9.13 | 7 / 23 | |
| 0.9.12 | 7 / 23 | |
| 0.9.11 | 7 / 23 | |
| 0.9.10 | 7 / 23 | |
| 0.9.9 | 6 / 23 | |
| 0.9.8 | 6 / 23 | |
| 0.9.7 | 6 / 23 | |
| 0.9.6 | 6 / 23 | |
| 0.9.5 | 6 / 23 | |
| 0.9.4 | 6 / 23 | |
| 0.9.3 | 6 / 23 | |
| 0.9.2 | 6 / 23 | |
| 0.9.1 | 6 / 23 | |
| 0.9.0 | 6 / 23 | |
| 0.8.8 | 6 / 23 | |
| 0.8.7 | 6 / 23 | |
| 0.8.6 | 6 / 22 | |
| 0.8.5 | 6 / 22 | |
| 0.8.4 | 6 / 22 | |
| 0.8.2 | 6 / 22 | |
| 0.8.1 | 6 / 22 | |
| 0.8.0 | 5 / 23 | |
| 0.7.5 | 5 / 23 | |
| 0.7.4 | 5 / 23 | |
| 0.7.3 | 5 / 23 | |
| 0.7.2 | 5 / 23 | |
| 0.7.1 | 4 / 24 | |
| 0.7.0 | 4 / 24 | |
| 0.6.13 | 4 / 19 | |
| 0.6.12 | 4 / 19 | |
| 0.6.11 | 4 / 19 | |
| 0.6.10 | 4 / 19 | |
| 0.6.9 | 4 / 19 |
v0.11.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
2 findingsThis version was published by a different npm account than previous versions on 2025-04-24. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.8
2 findingsThis version was published by a different npm account than previous versions on 2025-04-08. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.7
2 findingsThis version was published by a different npm account than previous versions on 2025-04-03. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.6
2 findingsThis version was published by a different npm account than previous versions on 2025-03-19. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.4
2 findingsThis version was published by a different npm account than previous versions on 2025-02-27. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
2 findingsThis version was published by a different npm account than previous versions on 2025-02-21. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
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 (aleobrent) than the most recent previously approved version (christianwwwwwwww) on 2025-02-20, but aleobrent 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.8.0
2 findingsThis version was published by a different npm account than previous versions on 2025-01-24. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.5
2 findingsThis version was published by a different npm account than previous versions on 2024-12-20. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
2 findingsThis version was published by a different npm account than previous versions on 2024-12-20. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
2 findingsThis version was published by a different npm account than previous versions on 2024-12-20. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
2 findingsThis version was published by a different npm account than previous versions on 2024-12-19. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
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 (aleobrent) than the most recent previously approved version (christianwwwwwwww) on 2024-09-27, but aleobrent 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.6.13
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 (christianwwwwwwww) than the most recent previously approved version (aleobrent) on 2024-08-06, but christianwwwwwwww 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.6.12
2 findingsThis version was published by a different npm account than previous versions on 2024-08-05. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.