@checkstack/catalog-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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@checkstack/automation-backend | AI (dependencies): Internal @checkstack namespace dep; consistent with publisher's established package ecosystem. | ai | |
| dependencies | unvetted-dep:@checkstack/ai-backend | AI (dependencies): Internal @checkstack namespace dep; consistent with publisher's established package ecosystem. | ai | |
| dependencies | unvetted-dep:@checkstack/ai-common | AI (dependencies): Internal @checkstack namespace dep; consistent with publisher's established package ecosystem. | ai | |
| provenance | missing-githead | AI (provenance): Established publisher with strong track record; no other risk signals; likely a CI/CD environment change. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all @checkstack/* packages; org does not use Sigstore CI provenance. | ai | |
| phantom-deps | phantom-dep:@orpc/contract | AI (phantom-deps): Used in config/type-level files in a TypeScript monorepo; not a direct import but a legitimate declared dep. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is an internal @checkstack-scoped package; consistent with the rest of the dependency tree. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): Monorepo package; zod likely used transitively or re-exported via workspace deps. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent with private/internal package pattern across the @checkstack namespace. | ai | |
| phantom-deps | phantom-dep:hono | AI (phantom-deps): hono is declared as a runtime dep and referenced in config; phantom-dep heuristic is a false positive here. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal monorepo package; missing metadata is expected for private org packages, not a spam indicator. | ai |
Versions (showing 51 of 61)
| Version | Deps | Published |
|---|---|---|
| 1.4.11 | 20 / 8 | |
| 1.4.8 | 20 / 8 | |
| 1.4.7 | 20 / 8 | |
| 1.4.5 | 20 / 8 | |
| 1.4.2 | 20 / 8 | |
| 1.4.1 | 20 / 8 | |
| 1.4.0 | 20 / 8 | |
| 1.3.1 | 17 / 8 | |
| 1.3.0 | 17 / 8 | |
| 1.2.0 | 17 / 8 | |
| 1.1.6 | 16 / 7 | |
| 1.1.5 | 16 / 7 | |
| 1.1.4 | 16 / 7 | |
| 1.1.3 | 16 / 7 | |
| 1.1.2 | 16 / 7 | |
| 1.1.1 | 16 / 8 | |
| 1.1.0 | 16 / 8 | |
| 1.0.2 | 16 / 8 | |
| 1.0.1 | 16 / 8 | |
| 1.0.0 | 16 / 8 | |
| 0.7.1 | 16 / 7 | |
| 0.7.0 | 16 / 7 | |
| 0.6.1 | 14 / 7 | |
| 0.6.0 | 14 / 7 | |
| 0.5.4 | 14 / 7 | |
| 0.5.2 | 14 / 7 | |
| 0.5.1 | 14 / 7 | |
| 0.5.0 | 14 / 7 | |
| 0.4.4 | 14 / 7 | |
| 0.4.3 | 14 / 7 | |
| 0.4.2 | 14 / 7 | |
| 0.4.1 | 14 / 7 | |
| 0.3.0 | 14 / 7 | |
| 0.2.24 | 12 / 7 | |
| 0.2.23 | 12 / 7 | |
| 0.2.22 | 12 / 7 | |
| 0.2.21 | 12 / 7 | |
| 0.2.20 | 12 / 7 | |
| 0.2.19 | 12 / 7 | |
| 0.2.18 | 12 / 7 | |
| 0.2.17 | 12 / 7 | |
| 0.2.16 | 12 / 8 | |
| 0.2.15 | 12 / 8 | |
| 0.2.14 | 12 / 8 | |
| 0.2.13 | 12 / 8 | |
| 0.2.12 | 12 / 8 | |
| 0.2.11 | 12 / 8 | |
| 0.2.10 | 12 / 8 | |
| 0.2.9 | 10 / 8 | |
| 0.2.8 | 10 / 8 | |
| 0.2.7 | 10 / 8 |
v1.4.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.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.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.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.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.19
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.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.17
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.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.15
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.14
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.13
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.12
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
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.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.