@checkstack/healthcheck-tcp-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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@checkstack/backend-api | AI (dependencies): Internal monorepo sibling under same @checkstack scope; workspace:* is not a real external dependency. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal scoped monorepo package; missing metadata is expected for private org packages, not a spam/malware indicator. | ai | |
| license | uncommon-license:Elastic-2.0 | AI (license): Elastic-2.0 is a known license used consistently across this package family; not a security risk. | ai |
Versions (showing 64 of 64)
| Version | Deps | Published |
|---|---|---|
| 0.5.4 | 3 / 4 | |
| 0.5.3 | 3 / 4 | |
| 0.5.2 | 3 / 4 | |
| 0.5.1 | 3 / 4 | |
| 0.5.0 | 3 / 4 | |
| 0.4.9 | 3 / 4 | |
| 0.4.8 | 3 / 4 | |
| 0.4.7 | 3 / 4 | |
| 0.4.6 | 3 / 4 | |
| 0.4.5 | 3 / 4 | |
| 0.4.4 | 3 / 4 | |
| 0.4.3 | 3 / 4 | |
| 0.4.2 | 3 / 4 | |
| 0.4.1 | 3 / 4 | |
| 0.4.0 | 3 / 4 | |
| 0.3.11 | 3 / 4 | |
| 0.3.10 | 3 / 4 | |
| 0.3.9 | 3 / 4 | |
| 0.3.8 | 3 / 4 | |
| 0.3.7 | 3 / 4 | |
| 0.3.6 | 3 / 4 | |
| 0.3.5 | 3 / 4 | |
| 0.3.4 | 3 / 4 | |
| 0.3.3 | 3 / 4 | |
| 0.3.2 | 3 / 4 | |
| 0.3.1 | 3 / 4 | |
| 0.3.0 | 3 / 4 | |
| 0.2.23 | 3 / 4 | |
| 0.2.22 | 3 / 4 | |
| 0.2.21 | 3 / 4 | |
| 0.2.20 | 3 / 4 | |
| 0.2.19 | 3 / 4 | |
| 0.2.18 | 3 / 4 | |
| 0.2.17 | 3 / 4 | |
| 0.2.16 | 3 / 4 | |
| 0.2.15 | 3 / 4 | |
| 0.2.14 | 3 / 4 | |
| 0.2.13 | 3 / 4 | |
| 0.2.12 | 3 / 4 | |
| 0.2.11 | 3 / 4 | |
| 0.2.10 | 3 / 4 | |
| 0.2.9 | 3 / 4 | |
| 0.2.8 | 3 / 4 | |
| 0.2.7 | 3 / 4 | |
| 0.2.6 | 3 / 4 | |
| 0.2.5 | 3 / 4 | |
| 0.2.4 | 3 / 4 | |
| 0.2.3 | 3 / 4 | |
| 0.1.13 | 3 / 4 | |
| 0.1.12 | 3 / 4 | |
| 0.1.11 | 3 / 4 | |
| 0.1.10 | 3 / 4 | |
| 0.1.9 | 3 / 4 | |
| 0.1.8 | 3 / 4 | |
| 0.1.7 | 3 / 4 | |
| 0.1.6 | 3 / 4 | |
| 0.1.5 | 3 / 4 | |
| 0.1.4 | 3 / 4 | |
| 0.1.3 | 3 / 4 | |
| 0.1.2 | 3 / 4 | |
| 0.1.1 | 3 / 4 | |
| 0.1.0 | 3 / 4 | |
| 0.0.3 | 3 / 4 | |
| 0.0.2 | 3 / 4 |
v0.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.