@checkstack/maintenance-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 — 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/automation-common | AI (phantom-deps): Same-org package used indirectly; stable false positive for this monorepo-style package. | ai | |
| dependencies | unvetted-dep:@checkstack/ai-common | AI (dependencies): Same-org @checkstack/* package; consistent with monorepo pattern across all versions. | ai | |
| dependencies | unvetted-dep:@checkstack/ai-backend | AI (dependencies): Same-org @checkstack/* package; consistent with monorepo pattern across all versions. | ai | |
| dependencies | unvetted-dep:@checkstack/automation-common | AI (dependencies): Same-org @checkstack/* package; consistent with monorepo pattern across all versions. | ai | |
| dependencies | unvetted-dep:@checkstack/automation-backend | AI (dependencies): Same-org @checkstack/* package; consistent with monorepo pattern across all versions. | ai | |
| phantom-deps | phantom-dep:@orpc/contract | AI (phantom-deps): Referenced in config/contract files rather than direct imports; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@checkstack/catalog-backend | AI (phantom-deps): Same-org internal dep; phantom detection unreliable for monorepo packages. | ai | |
| provenance | no-provenance | AI (provenance): No provenance across all @checkstack/* packages; consistent internal publishing pattern. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal monorepo workspace package; missing metadata is expected, not a spam/malware indicator. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal monorepo package; no description is normal for workspace-only packages. | ai | |
| phantom-deps | phantom-dep:@checkstack/integration-common | AI (phantom-deps): Same-org workspace dep; phantom-dep heuristic unreliable for monorepo packages. | ai | |
| phantom-deps | phantom-dep:@checkstack/notification-common | AI (phantom-deps): Same-org workspace dep; phantom-dep heuristic unreliable for monorepo packages. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 1.4.0 | 19 / 7 | |
| 1.3.0 | 16 / 7 | |
| 1.1.6 | 16 / 7 | |
| 1.1.4 | 16 / 7 | |
| 1.0.2 | 16 / 7 | |
| 0.7.1 | 15 / 6 | |
| 0.6.0 | 13 / 6 | |
| 0.5.14 | 13 / 6 | |
| 0.5.13 | 13 / 6 | |
| 0.5.12 | 13 / 6 | |
| 0.5.9 | 13 / 6 | |
| 0.5.5 | 12 / 8 | |
| 0.5.4 | 12 / 8 | |
| 0.5.2 | 11 / 8 | |
| 0.5.1 | 11 / 8 | |
| 0.2.5 | 11 / 8 | |
| 0.2.4 | 11 / 8 | |
| 0.1.0 | 11 / 8 | |
| 0.0.3 | 11 / 8 | |
| 0.0.2 | 11 / 8 |
v1.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.6
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.
v1.1.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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.4
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.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4
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. 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.