@checkstack/notification-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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@checkstack/signal-frontend | AI (phantom-deps): Same org scope; likely re-exported or used indirectly via another @checkstack dep. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal scoped org package; missing description is consistent across all @checkstack packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal monorepo package; no repo/homepage/keywords is expected for private org packages. | ai | |
| provenance | no-provenance | AI (provenance): No provenance across all @checkstack packages; consistent pattern, not a per-version anomaly. | ai |
Versions (showing 35 of 35)
| Version | Deps | Published |
|---|---|---|
| 0.5.5 | 10 / 4 | |
| 0.5.4 | 10 / 4 | |
| 0.5.3 | 10 / 4 | |
| 0.5.2 | 10 / 4 | |
| 0.5.1 | 10 / 4 | |
| 0.5.0 | 10 / 4 | |
| 0.4.7 | 10 / 4 | |
| 0.4.6 | 10 / 4 | |
| 0.4.5 | 10 / 4 | |
| 0.4.4 | 10 / 4 | |
| 0.4.3 | 10 / 4 | |
| 0.4.2 | 10 / 4 | |
| 0.4.1 | 10 / 4 | |
| 0.4.0 | 10 / 4 | |
| 0.3.1 | 9 / 4 | |
| 0.3.0 | 9 / 4 | |
| 0.2.35 | 9 / 4 | |
| 0.2.20 | 9 / 4 | |
| 0.2.11 | 9 / 4 | |
| 0.2.10 | 9 / 4 | |
| 0.2.9 | 9 / 4 | |
| 0.2.8 | 9 / 4 | |
| 0.2.7 | 9 / 4 | |
| 0.2.6 | 9 / 4 | |
| 0.2.5 | 9 / 4 | |
| 0.2.4 | 9 / 4 | |
| 0.2.3 | 9 / 4 | |
| 0.2.2 | 9 / 4 | |
| 0.2.1 | 9 / 4 | |
| 0.2.0 | 9 / 4 | |
| 0.1.0 | 9 / 4 | |
| 0.0.5 | 9 / 4 | |
| 0.0.4 | 9 / 4 | |
| 0.0.3 | 9 / 4 | |
| 0.0.2 | 9 / 4 |
v0.5.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.20
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: enyineer.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.