@checkstack/theme-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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Established @checkstack org publisher with strong approval history; missing gitHead likely reflects a CI change, not a supply-chain issue. | ai | |
| dependencies | unvetted-dep:@orpc/server | AI (dependencies): Standard RPC server library added as a runtime dep; no malware indicators and consistent with backend theme package usage. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal scoped package; missing description is stable across versions. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is consistent across all @checkstack packages; not a per-version concern. | ai | |
| dependencies | unvetted-dep:@checkstack/backend-api | AI (dependencies): workspace:* protocol indicates monorepo sibling, not an external unvetted dependency. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal monorepo package; missing metadata is expected for private workspace packages. | ai | |
| dependencies | unvetted-dep:@checkstack/auth-backend | AI (dependencies): workspace:* protocol indicates monorepo sibling, not an external unvetted dependency. | ai | |
| dependencies | unvetted-dep:@checkstack/theme-common | AI (dependencies): workspace:* protocol indicates monorepo sibling, not an external unvetted dependency. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): zod is a peer/transitive dep in a monorepo context; phantom-dep false positive stable for this package. | ai | |
| phantom-deps | phantom-dep:@checkstack/common | AI (phantom-deps): Same-org scoped package; phantom-dep heuristic unreliable for monorepo internal deps. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 0.2.4 | 7 / 7 | |
| 0.2.3 | 7 / 7 | |
| 0.2.2 | 7 / 7 | |
| 0.2.1 | 7 / 7 | |
| 0.2.0 | 7 / 7 | |
| 0.1.37 | 7 / 7 | |
| 0.1.36 | 7 / 7 | |
| 0.1.35 | 7 / 7 | |
| 0.1.34 | 7 / 7 | |
| 0.1.33 | 7 / 7 | |
| 0.1.32 | 7 / 7 | |
| 0.1.31 | 7 / 7 | |
| 0.1.28 | 7 / 7 | |
| 0.1.27 | 7 / 7 | |
| 0.1.26 | 7 / 7 | |
| 0.1.25 | 7 / 6 | |
| 0.1.24 | 7 / 6 | |
| 0.1.23 | 7 / 6 | |
| 0.1.19 | 7 / 6 | |
| 0.1.16 | 7 / 6 | |
| 0.1.15 | 7 / 6 | |
| 0.1.14 | 6 / 8 | |
| 0.1.13 | 6 / 8 | |
| 0.1.11 | 6 / 8 | |
| 0.1.7 | 6 / 8 | |
| 0.1.4 | 6 / 8 | |
| 0.1.2 | 6 / 8 | |
| 0.1.1 | 6 / 8 | |
| 0.1.0 | 6 / 8 | |
| 0.0.4 | 6 / 8 | |
| 0.0.3 | 6 / 8 | |
| 0.0.2 | 6 / 8 |
v0.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.16
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.1.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
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.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.