@checkstack/healthcheck-frontend No license 30 versions

@checkstack/healthcheck-frontend

npm

30

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; publisher has strong approval track record.	ai	2026/06/07
dependencies	unvetted-dep:@checkstack/script-packages-frontend	AI (dependencies): Same-org @checkstack namespace; consistent with other approved deps in this monorepo.	ai	2026/06/07
phantom-deps	phantom-dep:prismjs	AI (phantom-deps): Direct runtime dependency in code editor component; false positive for workspace package.	ai	2026/06/01
phantom-deps	phantom-dep:@types/prismjs	AI (phantom-deps): Type definitions for prismjs; false positive for workspace package.	ai	2026/06/01
phantom-deps	phantom-dep:react-simple-code-editor	AI (phantom-deps): Direct runtime dependency in code editor component; false positive for workspace package.	ai	2026/06/01
publish-pattern	new-deps-added	AI (publish-pattern): New dep is within the same @checkstack org namespace; consistent with internal monorepo dependency pattern.	ai	2026/05/31
bogus-package	bogus-package	AI (bogus-package): Internal org package in a monorepo; missing metadata is expected, not a spam/malware indicator.	ai	2026/05/26
phantom-deps	phantom-dep:ajv	AI (phantom-deps): ajv used in config files (e.g. schema validation config); not a phantom dep concern.	ai	2026/05/26
npm-metadata	no-description	AI (npm-metadata): Internal scoped package; missing description is consistent across the @checkstack org.	ai	2026/05/26
phantom-deps	phantom-dep:ajv-formats	AI (phantom-deps): Companion to ajv; used in config context, stable false positive for this package.	ai	2026/05/26
phantom-deps	phantom-dep:zod	AI (phantom-deps): zod referenced in config files; stable false positive for this package.	ai	2026/05/26

Versions (showing 30 of 30)

Version	Deps	Published
0.23.4	24 / 4	2026-06-06
0.22.0	23 / 4	2026-05-31
0.21.0	21 / 4	2026-05-30
0.19.5	21 / 4	2026-05-26
0.17.0	20 / 4	2026-04-29
0.13.5	18 / 4	2026-04-21
0.13.3	18 / 4	2026-04-20
0.10.0	18 / 5	2026-01-23
0.8.0	18 / 5	2026-01-21
0.7.2	18 / 5	2026-01-21
0.7.1	18 / 5	2026-01-21
0.7.0	18 / 5	2026-01-21
0.6.0	18 / 5	2026-01-20
0.5.0	18 / 5	2026-01-20
0.4.10	18 / 5	2026-01-18
0.4.9	18 / 5	2026-01-18
0.4.8	18 / 5	2026-01-17
0.4.7	18 / 5	2026-01-17
0.4.6	19 / 5	2026-01-17
0.4.5	19 / 5	2026-01-17
0.4.4	19 / 5	2026-01-17
0.4.3	19 / 5	2026-01-17
0.4.2	18 / 5	2026-01-17
0.4.1	18 / 5	2026-01-16
0.4.0	18 / 5	2026-01-16
0.3.0	17 / 5	2026-01-14
0.2.0	17 / 5	2026-01-13
0.1.0	17 / 4	2026-01-10
0.0.3	17 / 4	2026-01-09
0.0.2	17 / 4	2026-01-09

v0.23.4

1 finding

LOW No provenance attestation provenance

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

v0.22.0

1 finding

LOW No provenance attestation provenance

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

v0.21.0

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: enyineer.

LOW No provenance attestation provenance

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

v0.19.5

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: enyineer.

LOW No provenance attestation provenance

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

v0.17.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.13.5

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.13.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.10.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.8.0

1 finding

LOW No provenance attestation provenance

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

v0.7.2

1 finding

LOW No provenance attestation provenance

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

v0.7.1

1 finding

LOW No provenance attestation provenance

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

v0.7.0

1 finding

LOW No provenance attestation provenance

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

v0.6.0

1 finding

LOW No provenance attestation provenance

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

v0.5.0

1 finding

LOW No provenance attestation provenance

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

v0.4.10

1 finding

LOW No provenance attestation provenance

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

v0.4.9

1 finding

LOW No provenance attestation provenance

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

v0.4.8

1 finding

LOW No provenance attestation provenance

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

v0.4.7

1 finding

LOW No provenance attestation provenance

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

v0.4.6

1 finding

LOW No provenance attestation provenance

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

v0.4.5

1 finding

LOW No provenance attestation provenance

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

v0.4.4

1 finding

LOW No provenance attestation provenance

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

v0.4.3

1 finding

LOW No provenance attestation provenance

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

v0.4.2

1 finding

LOW No provenance attestation provenance

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

v0.4.1

1 finding

LOW No provenance attestation provenance

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

v0.4.0

1 finding

LOW No provenance attestation provenance

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

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.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.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.