@qnsp/browser-sdk
Browser-compatible PQC encryption SDK for QNSP. Client-side encryption, signing, and key encapsulation using NIST FIPS 203/204/205 standards via @noble/post-quantum.
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@noble/hashes | AI (phantom-deps): Declared dependency used in config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@qnsp/kms-client | AI (phantom-deps): Internal org dependency; legitimately declared and used. | ai | |
| phantom-deps | phantom-dep:@qnsp/storage-sdk | AI (phantom-deps): Internal org dependency; legitimately declared and used. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.1.4 | 5 / 3 | |
| 0.1.3 | 5 / 3 | |
| 0.1.2 | 5 / 3 | |
| 0.1.1 | 5 / 3 | |
| 0.1.0 | 5 / 3 |
v0.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
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.