@zkp2p/sdk
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/vaultUtils-CyPf4QGT.d.mts | AI (source-diff): TypeScript declaration file with long lines from bundled type exports; not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/vaultUtils-CyPf4QGT.d.ts | AI (source-diff): TypeScript declaration file with long lines from bundled type exports; not obfuscated code. | ai | |
| phantom-deps | phantom-dep:@zkp2p/core | AI (phantom-deps): Same-org monorepo sibling package; workspace:* dependency is a standard monorepo pattern, not a phantom dep risk. | ai | |
| dependencies | unvetted-dep:@zkp2p/core | AI (dependencies): Same-org sibling package in a monorepo workspace; not an external unvetted third-party dependency. | ai | |
| dependencies | unvetted-dep:@zkp2p/contracts-v2 | AI (dependencies): Same-org first-party dependency from the zkp2p organization; expected for this SDK package. | ai | |
| phantom-deps | phantom-dep:@zkp2p/contracts-v2 | AI (phantom-deps): Same-org dependency declared for type definitions or transitive use; not a security concern. | ai | |
| dependencies | unvetted-dep:ox | AI (dependencies): ox is a legitimate, well-known Ethereum primitives library; appropriate dependency for a Web3/ZKP SDK. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 0.4.0 | 5 / 22 | |
| 0.3.2 | 4 / 22 | |
| 0.3.1 | 4 / 22 | |
| 0.3.0 | 4 / 22 | |
| 0.2.4 | 4 / 22 | |
| 0.2.3 | 4 / 22 | |
| 0.2.1 | 4 / 22 | |
| 0.2.0 | 4 / 22 | |
| 0.1.1 | 4 / 22 | |
| 0.1.0 | 4 / 22 | |
| 0.0.15 | 3 / 18 | |
| 0.0.14 | 3 / 18 | |
| 0.0.13 | 3 / 18 | |
| 0.0.12 | 3 / 18 | |
| 0.0.10 | 3 / 18 | |
| 0.0.9 | 3 / 18 | |
| 0.0.8 | 3 / 18 | |
| 0.0.7 | 3 / 18 | |
| 0.0.6 | 3 / 17 | |
| 0.0.5 | 3 / 17 | |
| 0.0.4 | 4 / 17 | |
| 0.0.3 | 4 / 17 | |
| 0.0.2 | 4 / 17 | |
| 0.0.1 | 4 / 17 |
v0.4.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.