@checkstack/healthcheck-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 |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Internal monorepo package; missing description is consistent across all versions. | ai | |
| provenance | missing-githead | AI (provenance): Internal @checkstack monorepo package; publish environment change is plausible for a growing internal platform. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all @checkstack scoped packages; internal tooling pattern. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal monorepo package; missing public metadata is expected for workspace-scoped packages. | ai | |
| phantom-deps | phantom-dep:hono | AI (phantom-deps): Monorepo workspace package; hono likely imported transitively or via re-exports in sibling packages. | ai | |
| phantom-deps | phantom-dep:@hono/zod-validator | AI (phantom-deps): Same monorepo context; phantom-dep heuristic unreliable for workspace packages. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 1.2.0 | 24 / 9 | |
| 1.1.0 | 23 / 9 | |
| 0.10.6 | 17 / 8 | |
| 0.10.2 | 16 / 10 | |
| 0.4.1 | 14 / 8 | |
| 0.4.0 | 14 / 8 |
v1.2.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: enyineer.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.2
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.