← Home

@qnsp/search-sdk

npm Repository Homepage

TypeScript SDK for QNSP search-service (indexing, querying, SSE token helpers).

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-cryptographysearchvector-searchsemantic-searchencrypted-searchsse-xembeddingsml-kemnistfips-203quantum-safetypescriptnodejssdk

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@opentelemetry/api AI (phantom-deps): @opentelemetry/api is a declared runtime dep used in config/instrumentation; not directly imported in main code is expected for OTel setup patterns. ai
provenance no-provenance AI (provenance): No provenance is common (~88% of npm); no other risk signals present to elevate this. ai

Versions (showing 9 of 9)

Version Deps Published
0.2.10 9 / 3
0.2.9 9 / 3
0.2.8 9 / 3
0.2.7 9 / 3
0.2.6 9 / 3
0.2.5 8 / 3
0.2.4 8 / 3
0.2.3 8 / 3
0.2.2 8 / 3

v0.2.10

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

1 finding
INFO No provenance attestation provenance

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

v0.2.8

1 finding
INFO No provenance attestation provenance

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

v0.2.7

1 finding
INFO No provenance attestation provenance

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

v0.2.6

1 finding
INFO No provenance attestation provenance

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

v0.2.5

1 finding
LOW No provenance attestation provenance

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

v0.2.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.2.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.2.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.