@checkstack/anomaly-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:@orpc/contract | AI (phantom-deps): Used as a type/contract dep in config; not directly imported in source is expected for this package type. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal org package; missing description is consistent with monorepo conventions. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is common; no other risk signals elevate this. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal monorepo service package; missing metadata is expected for private org packages, not a spam indicator. | ai | |
| phantom-deps | phantom-dep:hono | AI (phantom-deps): hono is a runtime dep used via @orpc/server or framework config; stable FP for this package. | ai | |
| phantom-deps | phantom-dep:@checkstack/catalog-backend | AI (phantom-deps): Same-org dep likely re-exported or used as plugin registration; stable FP. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 1.2.2 | 20 / 8 | |
| 1.2.1 | 20 / 8 | |
| 1.2.0 | 20 / 8 | |
| 1.1.9 | 18 / 8 | |
| 1.1.8 | 18 / 8 | |
| 1.1.7 | 18 / 8 | |
| 1.1.6 | 18 / 8 | |
| 1.1.5 | 18 / 8 | |
| 1.1.4 | 18 / 8 | |
| 1.1.3 | 18 / 8 | |
| 1.1.2 | 18 / 8 | |
| 1.1.1 | 18 / 8 | |
| 1.1.0 | 18 / 8 | |
| 1.0.3 | 16 / 8 | |
| 1.0.2 | 16 / 8 | |
| 1.0.1 | 16 / 8 | |
| 1.0.0 | 16 / 8 | |
| 0.2.1 | 13 / 7 | |
| 0.2.0 | 13 / 7 |
v1.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.7
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.3
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.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.