@checkstack/integration-common
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Internal scoped package under @checkstack org; missing metadata is expected for private/internal libs. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal package; missing description is consistent with org-internal tooling pattern. | ai | |
| phantom-deps | phantom-dep:@orpc/contract | AI (phantom-deps): @orpc/contract is declared as a runtime dep and likely re-exported; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 0.9.10 | 4 / 3 | |
| 0.9.9 | 4 / 3 | |
| 0.9.8 | 4 / 3 | |
| 0.9.7 | 4 / 3 | |
| 0.9.6 | 4 / 3 | |
| 0.9.5 | 4 / 3 | |
| 0.9.4 | 4 / 3 | |
| 0.9.3 | 4 / 3 | |
| 0.9.2 | 4 / 3 | |
| 0.9.1 | 4 / 3 | |
| 0.9.0 | 4 / 3 | |
| 0.8.0 | 4 / 3 | |
| 0.7.3 | 4 / 3 | |
| 0.7.2 | 4 / 3 | |
| 0.7.1 | 4 / 3 | |
| 0.7.0 | 4 / 3 | |
| 0.6.0 | 4 / 3 | |
| 0.5.0 | 4 / 3 | |
| 0.4.0 | 4 / 3 | |
| 0.3.1 | 4 / 3 | |
| 0.3.0 | 4 / 3 | |
| 0.2.5 | 4 / 3 | |
| 0.2.4 | 4 / 3 | |
| 0.2.3 | 4 / 3 | |
| 0.2.2 | 4 / 3 | |
| 0.2.1 | 4 / 3 | |
| 0.2.0 | 4 / 3 | |
| 0.1.0 | 4 / 3 | |
| 0.0.4 | 4 / 3 | |
| 0.0.3 | 4 / 3 | |
| 0.0.2 | 4 / 3 |
v0.9.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.