@checkstack/backend
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:base64-decode | AI (semgrep): Decoding DB-stored tarball blobs; not obfuscation. Stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:better-auth | AI (phantom-deps): Declared in package.json dependencies; workspace monorepo pattern — likely re-exported or used indirectly. | ai | |
| phantom-deps | phantom-dep:@hono/zod-validator | AI (phantom-deps): Declared in package.json dependencies; workspace monorepo pattern — likely re-exported or used indirectly. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Standard Proxy handler using Reflect.get(); not obfuscation. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal monorepo package; missing description is expected. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Signals match private monorepo pattern (no repo URL, no keywords, no description). | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 0.17.2 | 25 / 7 | |
| 0.17.1 | 25 / 7 | |
| 0.17.0 | 25 / 7 | |
| 0.16.2 | 25 / 7 | |
| 0.16.1 | 25 / 7 | |
| 0.16.0 | 25 / 7 | |
| 0.15.0 | 25 / 7 | |
| 0.14.0 | 25 / 7 | |
| 0.13.0 | 25 / 7 | |
| 0.12.0 | 25 / 7 | |
| 0.11.0 | 25 / 7 | |
| 0.10.4 | 25 / 7 | |
| 0.10.3 | 25 / 7 | |
| 0.10.2 | 25 / 7 | |
| 0.8.0 | 22 / 6 | |
| 0.7.1 | 22 / 5 | |
| 0.6.4 | 21 / 5 | |
| 0.6.3 | 21 / 5 | |
| 0.5.0 | 21 / 5 | |
| 0.4.15 | 21 / 5 | |
| 0.4.14 | 20 / 6 | |
| 0.3.1 | 20 / 6 |
v0.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.