← Home

@qnsp/crypto-inventory-sdk

npm Repository Homepage

TypeScript SDK client for the QNSP crypto-inventory-service API. Provides cryptographic asset discovery and inventory management.

7
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-cryptographycrypto-inventorycbomcryptographic-bill-of-materialsasset-discoverypqc-migrationnist-pqcnistquantum-safequantum-resistantzero-trusttypescriptnodejssdk

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:shady-links-raw-ip AI (semgrep): Raw IP is 127.0.0.1 in a test helper mock server — not a real network exfiltration risk. ai
phantom-deps phantom-dep:undici AI (phantom-deps): undici is declared as a runtime dependency; phantom-dep heuristic fires because it's used indirectly via fetch/HTTP internals. ai

Versions (showing 7 of 7)

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.2 7 / 3
0.3.1 7 / 3
0.3.0 6 / 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. Consider requesting the maintainer enable provenance via CI/CD.

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