@checkstack/anomaly-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 — the axios compromise (March 2026) relied on exactly this gap.
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 monorepo package; missing metadata is expected for private org packages. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal @checkstack org package; no public description is consistent across their packages. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): Likely used transitively or in config/type files; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@checkstack/signal-frontend | AI (phantom-deps): Same org scope; likely re-exported or used in type declarations rather than direct imports. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 0.5.4 | 15 / 4 | |
| 0.5.3 | 15 / 4 | |
| 0.5.2 | 15 / 4 | |
| 0.5.1 | 15 / 4 | |
| 0.5.0 | 15 / 4 | |
| 0.4.8 | 15 / 4 | |
| 0.4.7 | 15 / 4 | |
| 0.4.6 | 15 / 4 | |
| 0.4.5 | 15 / 4 | |
| 0.4.4 | 15 / 4 | |
| 0.4.3 | 15 / 4 | |
| 0.4.2 | 15 / 4 | |
| 0.4.1 | 15 / 4 | |
| 0.4.0 | 15 / 4 | |
| 0.3.1 | 15 / 4 | |
| 0.3.0 | 15 / 4 | |
| 0.2.2 | 13 / 4 | |
| 0.2.1 | 13 / 4 | |
| 0.2.0 | 13 / 4 |
v0.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
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.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.