@checkstack/signal-frontend
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): Same pattern across all @checkstack packages; not indicative of malice. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped internal/org package; sparse metadata is expected for private/monorepo packages. | ai |
Versions (showing 36 of 36)
| Version | Deps | Published |
|---|---|---|
| 0.3.7 | 1 / 4 | |
| 0.3.6 | 1 / 4 | |
| 0.3.5 | 1 / 4 | |
| 0.3.4 | 1 / 4 | |
| 0.3.3 | 1 / 4 | |
| 0.3.2 | 1 / 4 | |
| 0.3.1 | 1 / 4 | |
| 0.3.0 | 1 / 4 | |
| 0.2.6 | 1 / 4 | |
| 0.2.5 | 1 / 4 | |
| 0.2.4 | 1 / 4 | |
| 0.2.3 | 1 / 4 | |
| 0.2.2 | 1 / 4 | |
| 0.2.1 | 1 / 4 | |
| 0.2.0 | 1 / 4 | |
| 0.1.5 | 1 / 4 | |
| 0.1.4 | 1 / 4 | |
| 0.1.3 | 1 / 4 | |
| 0.1.2 | 1 / 4 | |
| 0.1.1 | 1 / 4 | |
| 0.1.0 | 1 / 4 | |
| 0.0.16 | 1 / 4 | |
| 0.0.15 | 1 / 4 | |
| 0.0.14 | 1 / 4 | |
| 0.0.13 | 1 / 4 | |
| 0.0.12 | 1 / 4 | |
| 0.0.11 | 1 / 4 | |
| 0.0.10 | 1 / 4 | |
| 0.0.9 | 1 / 4 | |
| 0.0.8 | 1 / 4 | |
| 0.0.7 | 1 / 4 | |
| 0.0.6 | 1 / 4 | |
| 0.0.5 | 1 / 4 | |
| 0.0.4 | 1 / 4 | |
| 0.0.3 | 1 / 4 | |
| 0.0.2 | 1 / 4 |
v0.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.