← Home

@qnsp/storage-sdk

npm Repository Homepage

TypeScript SDK client for the QNSP storage-service API.

9
Versions
Apache-2.0
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

cuilabs

Keywords

qnsppqcpost-quantumpost-quantum-cryptographystoragesse-xencrypted-storageobject-storages3-compatibleencryption-at-restml-kemnistfips-203quantum-safezero-trusttypescriptnodejssdk

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@opentelemetry/api AI (phantom-deps): Referenced in config files; stable false positive for this package. ai
phantom-deps phantom-dep:zod AI (phantom-deps): zod is declared as a runtime dep in package.json; phantom-dep heuristic false positive for this SDK. ai
phantom-deps phantom-dep:undici AI (phantom-deps): undici is declared as a runtime dep; known implicit/runtime usage pattern, stable false positive. ai

Versions (showing 9 of 9)

Version Deps Published
0.3.6 7 / 3
0.3.5 7 / 3
0.3.4 7 / 3
0.3.3 7 / 3
0.3.0 6 / 3
0.2.1 6 / 3
0.1.0 6 / 3
0.0.2 6 / 3
0.0.1 7 / 3

v0.3.6

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.3.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.4

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.3.3

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.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.2

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.0.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.