@checkstack/healthcheck-http-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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Established publisher with strong track record; missing gitHead appears to be a CI environment change, not a supply-chain indicator. | ai | |
| license | uncommon-license:Elastic-2.0 | AI (license): Elastic-2.0 is the declared license for this package family; stable across versions. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal @checkstack scoped package; missing metadata is consistent across the org's packages, not a spam indicator. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal scoped package; missing description is a stable pattern for this org. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all versions of this package; no CI provenance setup in place for this org. | ai | |
| phantom-deps | phantom-dep:jsonpath-plus | AI (phantom-deps): jsonpath-plus is a declared runtime dependency; phantom-dep fires due to indirect/config usage pattern stable for this package. | ai |
Versions (showing 51 of 55)
| Version | Deps | Published |
|---|---|---|
| 0.5.1 | 4 / 4 | |
| 0.5.0 | 4 / 4 | |
| 0.4.11 | 4 / 4 | |
| 0.4.10 | 4 / 4 | |
| 0.4.9 | 4 / 4 | |
| 0.4.8 | 4 / 4 | |
| 0.4.7 | 4 / 4 | |
| 0.4.6 | 4 / 4 | |
| 0.4.5 | 4 / 4 | |
| 0.4.4 | 4 / 4 | |
| 0.4.3 | 4 / 4 | |
| 0.4.2 | 4 / 4 | |
| 0.4.1 | 4 / 4 | |
| 0.4.0 | 4 / 4 | |
| 0.3.23 | 4 / 4 | |
| 0.3.22 | 4 / 4 | |
| 0.3.21 | 4 / 4 | |
| 0.3.20 | 4 / 4 | |
| 0.3.19 | 4 / 4 | |
| 0.3.18 | 4 / 4 | |
| 0.3.17 | 4 / 4 | |
| 0.3.16 | 4 / 4 | |
| 0.3.15 | 4 / 4 | |
| 0.3.14 | 4 / 4 | |
| 0.3.13 | 4 / 4 | |
| 0.3.12 | 4 / 4 | |
| 0.3.11 | 4 / 4 | |
| 0.3.10 | 4 / 4 | |
| 0.3.9 | 4 / 4 | |
| 0.3.8 | 4 / 4 | |
| 0.3.7 | 4 / 4 | |
| 0.3.6 | 4 / 4 | |
| 0.3.5 | 4 / 4 | |
| 0.3.4 | 4 / 4 | |
| 0.3.3 | 4 / 4 | |
| 0.3.2 | 4 / 5 | |
| 0.3.1 | 4 / 5 | |
| 0.3.0 | 4 / 5 | |
| 0.2.5 | 4 / 5 | |
| 0.2.4 | 4 / 5 | |
| 0.2.3 | 4 / 5 | |
| 0.2.2 | 4 / 5 | |
| 0.2.1 | 4 / 5 | |
| 0.2.0 | 4 / 5 | |
| 0.1.8 | 4 / 5 | |
| 0.1.7 | 4 / 5 | |
| 0.1.6 | 4 / 5 | |
| 0.1.5 | 4 / 5 | |
| 0.1.4 | 4 / 5 | |
| 0.1.3 | 4 / 5 | |
| 0.1.2 | 4 / 5 |
v0.3.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: enyineer.
v0.3.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: enyineer.
v0.2.5
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: enyineer.
v0.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.