@checkstack/catalog-backend No license 39 versions

@checkstack/catalog-backend

npm

39

Versions

—

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

enyineer

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	no-provenance	AI (provenance): Consistent across all @checkstack/* packages; org does not use Sigstore CI provenance.	ai	2026/06/07
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	2026/06/06
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	2026/06/01
phantom-deps	phantom-dep:zod	AI (phantom-deps): Monorepo package; zod likely used transitively or re-exported via workspace deps.	ai	2026/05/27
npm-metadata	no-description	AI (npm-metadata): Consistent with private/internal package pattern across the @checkstack namespace.	ai	2026/05/26
bogus-package	bogus-package	AI (bogus-package): Internal monorepo package; missing metadata is expected for private org packages, not a spam indicator.	ai	2026/05/21
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	2026/05/21

Versions (showing 39 of 39)

Version	Deps	Published
1.4.2	20 / 8	2026-06-05
1.4.0	20 / 8	2026-06-05
1.3.0	17 / 8	2026-05-31
1.2.0	17 / 8	2026-05-30
1.1.6	16 / 7	2026-05-29
1.1.5	16 / 7	2026-05-26
1.1.4	16 / 7	2026-05-26
1.1.3	16 / 7	2026-05-19
1.1.2	16 / 7	2026-05-13
1.1.1	16 / 8	2026-05-13
1.1.0	16 / 8	2026-05-04
1.0.1	16 / 8	2026-05-03
1.0.0	16 / 8	2026-04-30
0.7.0	16 / 7	2026-04-29
0.6.0	14 / 7	2026-04-27
0.5.0	14 / 7	2026-04-23
0.4.3	14 / 7	2026-04-23
0.3.0	14 / 7	2026-04-21
0.2.24	12 / 7	2026-04-19
0.2.23	12 / 7	2026-04-18
0.2.22	12 / 7	2026-04-18
0.2.21	12 / 7	2026-04-17
0.2.20	12 / 7	2026-04-17
0.2.18	12 / 7	2026-04-16
0.2.16	12 / 8	2026-04-15
0.2.10	12 / 8	2026-01-21
0.2.9	10 / 8	2026-01-21
0.2.8	10 / 8	2026-01-20
0.2.7	10 / 8	2026-01-18
0.2.6	10 / 8	2026-01-18
0.2.5	10 / 8	2026-01-17
0.2.4	10 / 8	2026-01-17
0.2.3	10 / 8	2026-01-16
0.2.2	10 / 8	2026-01-16
0.2.1	10 / 8	2026-01-15
0.2.0	10 / 8	2026-01-14
0.1.0	10 / 8	2026-01-13
0.0.3	10 / 8	2026-01-10
0.0.2	10 / 8	2026-01-09

v1.4.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.1.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.7.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.6.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.5.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.4.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.24

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.23

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.22

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.21

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.20

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.18

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.16

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.10

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.9

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.