@qnsp/auth-sdk
TypeScript SDK for QNSP post-quantum authentication: PQC-signed JWTs, WebAuthn passkeys, MFA, and OIDC federation. Zero-config — defaults to cloud.qnsp.cuilabs.io. Free API key required.
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 |
|---|---|---|---|---|
| semgrep | semgrep:etc-passwd-access | AI (semgrep): Appears only in test code asserting path-traversal is rejected; not a credential-harvesting vector. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): Raw IP 127.0.0.1 used only in test assertions; not a production network call. | ai | |
| phantom-deps | phantom-dep:undici | AI (phantom-deps): undici is explicitly listed as a runtime dependency in package.json; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 12 of 12)
| 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 | |
| 0.2.2 | 6 / 3 | |
| 0.2.1 | 6 / 3 | |
| 0.1.1 | 6 / 3 | |
| 0.0.2 | 6 / 3 | |
| 0.0.1 | 6 / 3 |
v0.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
2 findingsAccessing /etc/passwd or /etc/shadow — credential harvesting on Linux 131 | email: "[email protected]", 132 | password: "password", > 133 | tenantId: "../../etc/passwd", 134 | }), 135 | ).rejects.toThrow("Invalid tenantId");
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
2 findingsAccessing /etc/passwd or /etc/shadow — credential harvesting on Linux 125 | email: "[email protected]", 126 | password: "password", > 127 | tenantId: "../../etc/passwd", 128 | }), 129 | ).rejects.toThrow("Invalid tenantId");
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
2 findingsAccessing /etc/passwd or /etc/shadow — credential harvesting on Linux 120 | email: "[email protected]", 121 | password: "password", > 122 | tenantId: "../../etc/passwd", 123 | }), 124 | ).rejects.toThrow("Invalid tenantId");
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
2 findingsAccessing /etc/passwd or /etc/shadow — credential harvesting on Linux 120 | email: "[email protected]", 121 | password: "password", > 122 | tenantId: "../../etc/passwd", 123 | }), 124 | ).rejects.toThrow("Invalid tenantId");
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
2 findingsAccessing /etc/passwd or /etc/shadow — credential harvesting on Linux 120 | email: "[email protected]", 121 | password: "password", > 122 | tenantId: "../../etc/passwd", 123 | }), 124 | ).rejects.toThrow("Invalid tenantId");
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
2 findingsAccessing /etc/passwd or /etc/shadow — credential harvesting on Linux 120 | email: "[email protected]", 121 | password: "password", > 122 | tenantId: "../../etc/passwd", 123 | }), 124 | ).rejects.toThrow("Invalid tenantId");
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
2 findingsAccessing /etc/passwd or /etc/shadow — credential harvesting on Linux 120 | email: "[email protected]", 121 | password: "password", > 122 | tenantId: "../../etc/passwd", 123 | }), 124 | ).rejects.toThrow("Invalid tenantId");
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.