@checkstack/backend-api
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:hex-decode | AI (semgrep): Used in encryption.ts to parse AES key from hex string — standard crypto pattern, not obfuscation. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Used in encryption.ts to decode IV, auth tag, and ciphertext — standard AES-GCM decryption pattern. | ai | |
| phantom-deps | phantom-dep:hono | AI (phantom-deps): hono is declared as a peerDependency; phantom-dep false positive for peer deps. | ai | |
| phantom-deps | phantom-dep:@orpc/zod | AI (phantom-deps): Re-exported via config files rather than direct import; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@orpc/client | AI (phantom-deps): Re-exported via config files rather than direct import; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@orpc/openapi | AI (phantom-deps): Re-exported via config files rather than direct import; stable false positive for this package. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 0.15.3 | 14 / 3 | |
| 0.15.0 | 14 / 3 | |
| 0.14.1 | 14 / 3 | |
| 0.5.1 | 11 / 3 | |
| 0.5.0 | 11 / 3 | |
| 0.4.1 | 11 / 3 | |
| 0.4.0 | 11 / 3 | |
| 0.3.3 | 11 / 3 | |
| 0.3.2 | 11 / 3 | |
| 0.3.1 | 11 / 3 | |
| 0.3.0 | 11 / 3 | |
| 0.2.0 | 11 / 3 | |
| 0.1.0 | 11 / 3 | |
| 0.0.2 | 11 / 3 |
v0.15.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.