@qnsp/tenant-sdk
TypeScript SDK client for the QNSP tenant-service API. Provides tenant lifecycle and subscription management.
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:undici | AI (phantom-deps): undici is listed as a direct runtime dependency in package.json; phantom-dep heuristic is a false positive here. | ai | |
| semgrep | semgrep:etc-passwd-access | AI (semgrep): Fires on a test asserting path traversal is rejected; not credential harvesting. | ai |
Versions (showing 11 of 11)
| 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.0 | 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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 57 | 58 | it("should reject path traversal in tenantId", async () => { > 59 | await expect(client.getTenant("../../etc/passwd")).rejects.toThrow("Invalid id"); 60 | }); 61 |
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 51 | 52 | it("should reject path traversal in tenantId", async () => { > 53 | await expect(client.getTenant("../../etc/passwd")).rejects.toThrow("Invalid id"); 54 | }); 55 |
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
2 findingsAccessing /etc/passwd or /etc/shadow — credential harvesting on Linux 48 | 49 | it("should reject path traversal in tenantId", async () => { > 50 | await expect(client.getTenant("../../etc/passwd")).rejects.toThrow("Invalid id"); 51 | }); 52 |
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 48 | 49 | it("should reject path traversal in tenantId", async () => { > 50 | await expect(client.getTenant("../../etc/passwd")).rejects.toThrow("Invalid id"); 51 | }); 52 |
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 48 | 49 | it("should reject path traversal in tenantId", async () => { > 50 | await expect(client.getTenant("../../etc/passwd")).rejects.toThrow("Invalid id"); 51 | }); 52 |
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 48 | 49 | it("should reject path traversal in tenantId", async () => { > 50 | await expect(client.getTenant("../../etc/passwd")).rejects.toThrow("Invalid id"); 51 | }); 52 |
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.