@checkstack/collector-hardware-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): Private monorepo package; publish environment changes are plausible and no other risk signals present. | ai | |
| license | uncommon-license:Elastic-2.0 | AI (license): Elastic-2.0 is a recognized open-source license; stable for this package. | ai | |
| dependencies | unvetted-dep:@checkstack/backend-api | AI (dependencies): workspace:* sibling in a monorepo; not an external dependency risk. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal @checkstack scoped package; sparse metadata is expected for private monorepo components. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal scoped package; missing description is consistent across the @checkstack namespace. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all @checkstack/* packages; no provenance is expected for this private ecosystem. | ai |
Versions (showing 51 of 66)
| Version | Deps | Published |
|---|---|---|
| 0.1.65 | 4 / 4 | |
| 0.1.64 | 4 / 4 | |
| 0.1.63 | 4 / 4 | |
| 0.1.62 | 4 / 4 | |
| 0.1.61 | 4 / 4 | |
| 0.1.60 | 4 / 4 | |
| 0.1.59 | 4 / 4 | |
| 0.1.58 | 4 / 4 | |
| 0.1.57 | 4 / 4 | |
| 0.1.56 | 4 / 4 | |
| 0.1.55 | 4 / 4 | |
| 0.1.54 | 4 / 4 | |
| 0.1.53 | 4 / 4 | |
| 0.1.52 | 4 / 4 | |
| 0.1.51 | 4 / 4 | |
| 0.1.50 | 4 / 4 | |
| 0.1.49 | 4 / 4 | |
| 0.1.48 | 4 / 4 | |
| 0.1.47 | 4 / 4 | |
| 0.1.46 | 4 / 4 | |
| 0.1.45 | 4 / 4 | |
| 0.1.44 | 4 / 4 | |
| 0.1.43 | 4 / 4 | |
| 0.1.42 | 4 / 4 | |
| 0.1.41 | 4 / 4 | |
| 0.1.40 | 4 / 4 | |
| 0.1.39 | 4 / 4 | |
| 0.1.38 | 4 / 4 | |
| 0.1.37 | 4 / 4 | |
| 0.1.36 | 4 / 4 | |
| 0.1.35 | 4 / 4 | |
| 0.1.34 | 4 / 4 | |
| 0.1.33 | 4 / 4 | |
| 0.1.32 | 4 / 4 | |
| 0.1.31 | 4 / 4 | |
| 0.1.30 | 4 / 4 | |
| 0.1.29 | 4 / 4 | |
| 0.1.28 | 4 / 4 | |
| 0.1.27 | 4 / 4 | |
| 0.1.26 | 4 / 4 | |
| 0.1.25 | 4 / 4 | |
| 0.1.24 | 4 / 4 | |
| 0.1.23 | 4 / 4 | |
| 0.1.22 | 4 / 4 | |
| 0.1.21 | 4 / 4 | |
| 0.1.20 | 4 / 4 | |
| 0.1.19 | 4 / 4 | |
| 0.1.18 | 4 / 4 | |
| 0.1.17 | 4 / 4 | |
| 0.1.16 | 4 / 4 | |
| 0.1.15 | 4 / 4 |
v0.1.65
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.64
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.63
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.62
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.61
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.60
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.59
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.58
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.57
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.56
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.55
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.54
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.15
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.