@checkstack/maintenance-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 monorepo package; likely re-exported or used indirectly, stable false positive pattern. | ai | |
| phantom-deps | phantom-dep:@checkstack/notification-frontend | AI (phantom-deps): Same-org monorepo package; likely re-exported or used indirectly, stable false positive pattern. | ai | |
| phantom-deps | phantom-dep:@checkstack/notification-common | AI (phantom-deps): Same-org monorepo package; likely re-exported or used indirectly, stable false positive pattern. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is a workspace-internal @checkstack sibling, not an external package; no supply-chain risk. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is consistent across this org's packages; not a risk indicator here. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal monorepo package; missing description is a pattern across @checkstack packages, not a malice signal. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal org package in @checkstack monorepo; missing metadata is consistent across the ecosystem, not a spam indicator. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 0.8.5 | 15 / 4 | |
| 0.8.4 | 15 / 4 | |
| 0.8.3 | 15 / 4 | |
| 0.8.2 | 15 / 4 | |
| 0.8.1 | 15 / 4 | |
| 0.8.0 | 15 / 4 | |
| 0.7.8 | 15 / 4 | |
| 0.7.4 | 15 / 4 | |
| 0.5.8 | 12 / 4 | |
| 0.5.6 | 12 / 4 | |
| 0.5.3 | 12 / 4 | |
| 0.5.2 | 12 / 4 | |
| 0.5.1 | 12 / 4 | |
| 0.4.6 | 12 / 4 | |
| 0.4.5 | 12 / 4 | |
| 0.4.4 | 12 / 4 | |
| 0.4.3 | 12 / 4 | |
| 0.4.2 | 12 / 4 | |
| 0.4.1 | 12 / 4 | |
| 0.4.0 | 12 / 4 | |
| 0.3.6 | 12 / 4 | |
| 0.3.5 | 12 / 4 | |
| 0.3.4 | 12 / 4 | |
| 0.3.3 | 12 / 4 | |
| 0.3.2 | 12 / 4 | |
| 0.3.1 | 12 / 4 | |
| 0.3.0 | 12 / 4 | |
| 0.2.0 | 11 / 4 | |
| 0.1.0 | 11 / 4 | |
| 0.0.4 | 10 / 4 | |
| 0.0.3 | 10 / 4 | |
| 0.0.2 | 10 / 4 |
v0.8.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.8
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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 finding[Accepted risk] Package 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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
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.