@protocol-01/zkspl-sdk MIT 2 versions

@protocol-01/zkspl-sdk

npm Repository Homepage

SDK for Protocol 01 zkSPL confidential token balances

Versions

MIT

License

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

slashy_fx

Keywords

solanaprotocol-01privacyzero-knowledgezk-snarkgroth16confidentialzksplposeidon

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:bn.js	AI (phantom-deps): Declared dependency used indirectly through anchor; stable pattern for this SDK.	ai	2026/04/30
phantom-deps	phantom-dep:snarkjs	AI (phantom-deps): Declared dependency used indirectly through anchor; stable pattern for this SDK.	ai	2026/04/30
phantom-deps	phantom-dep:@solana/spl-token	AI (phantom-deps): Declared dependency used indirectly through anchor; stable pattern for this SDK.	ai	2026/04/30

Versions (showing 2 of 2)

Version	Deps	Published
0.1.1	7 / 6	2026-04-28
0.1.0	7 / 6	2026-04-28

v0.1.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.