@checkstack/signal-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 |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Internal @checkstack scoped package; missing description is a style issue, not a risk indicator. | ai | |
| dependencies | unvetted-dep:@checkstack/backend-api | AI (dependencies): Workspace-scoped sibling dep in a monorepo; not an external unvetted package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Private scoped monorepo package; missing metadata signals are expected, not spam indicators. | ai |
Versions (showing 51 of 53)
| Version | Deps | Published |
|---|---|---|
| 0.3.26 | 3 / 5 | |
| 0.3.25 | 3 / 5 | |
| 0.3.24 | 3 / 5 | |
| 0.3.23 | 3 / 5 | |
| 0.3.22 | 3 / 5 | |
| 0.3.21 | 3 / 5 | |
| 0.3.20 | 3 / 5 | |
| 0.3.19 | 3 / 5 | |
| 0.3.18 | 3 / 5 | |
| 0.3.17 | 3 / 5 | |
| 0.3.16 | 3 / 5 | |
| 0.3.15 | 3 / 5 | |
| 0.3.14 | 3 / 5 | |
| 0.3.13 | 3 / 5 | |
| 0.3.12 | 3 / 5 | |
| 0.3.11 | 3 / 5 | |
| 0.3.10 | 3 / 5 | |
| 0.3.9 | 3 / 5 | |
| 0.3.8 | 3 / 5 | |
| 0.3.7 | 3 / 5 | |
| 0.3.6 | 3 / 5 | |
| 0.3.5 | 3 / 5 | |
| 0.3.4 | 3 / 5 | |
| 0.3.3 | 3 / 5 | |
| 0.3.2 | 3 / 5 | |
| 0.3.1 | 3 / 5 | |
| 0.3.0 | 3 / 5 | |
| 0.2.12 | 3 / 5 | |
| 0.2.11 | 3 / 5 | |
| 0.2.10 | 3 / 5 | |
| 0.2.9 | 3 / 5 | |
| 0.2.8 | 3 / 5 | |
| 0.2.7 | 3 / 5 | |
| 0.2.6 | 3 / 5 | |
| 0.2.5 | 3 / 5 | |
| 0.2.4 | 3 / 5 | |
| 0.2.3 | 3 / 5 | |
| 0.2.2 | 3 / 5 | |
| 0.2.0 | 3 / 5 | |
| 0.1.17 | 3 / 5 | |
| 0.1.15 | 3 / 5 | |
| 0.1.8 | 3 / 5 | |
| 0.1.7 | 3 / 5 | |
| 0.1.6 | 3 / 5 | |
| 0.1.5 | 3 / 5 | |
| 0.1.4 | 3 / 5 | |
| 0.1.3 | 3 / 5 | |
| 0.1.2 | 3 / 5 | |
| 0.1.1 | 3 / 5 | |
| 0.1.0 | 3 / 5 | |
| 0.0.4 | 3 / 5 |
v0.3.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.