@qnsp/cli
QNSP CLI: manage keys, secrets, audit logs, and post-quantum cryptography from the terminal. Free tier at cloud.qnsp.cuilabs.io.
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped @qnsp/cli package; no relation to joi. Levenshtein match is coincidental. | ai | |
| phantom-deps | phantom-dep:@qnsp/auth-sdk | AI (phantom-deps): Same-org SDK dependency; likely used indirectly via CLI command modules. | ai | |
| phantom-deps | phantom-dep:@qnsp/audit-sdk | AI (phantom-deps): Same-org SDK dependency; likely used indirectly via CLI command modules. | ai | |
| phantom-deps | phantom-dep:@qnsp/vault-sdk | AI (phantom-deps): Same-org SDK dependency; likely used indirectly via CLI command modules. | ai | |
| phantom-deps | phantom-dep:@qnsp/kms-client | AI (phantom-deps): Same-org SDK dependency; likely used indirectly via CLI command modules. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.1.12 | 6 / 3 | |
| 0.1.11 | 6 / 3 | |
| 0.1.10 | 6 / 3 | |
| 0.1.9 | 6 / 3 | |
| 0.1.8 | 6 / 3 | |
| 0.1.7 | 6 / 3 | |
| 0.1.6 | 6 / 3 | |
| 0.1.5 | 6 / 3 | |
| 0.1.4 | 6 / 3 |
v0.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.