← Home

@checkstack/healthcheck-tls-backend

66
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

enyineer

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
license uncommon-license:Elastic-2.0 AI (license): Elastic-2.0 is a known, intentional license choice for this package family; stable across versions. ai
npm-metadata no-description AI (npm-metadata): Internal monorepo package; missing description is expected and stable across versions. ai
bogus-package bogus-package AI (bogus-package): Private @checkstack scoped package family; missing metadata is consistent across all versions, not a spam indicator. ai
provenance no-provenance AI (provenance): Consistent across all @checkstack packages; org hasn't adopted Sigstore yet. ai

Versions (showing 66 of 66)

Version Deps Published
0.4.4 3 / 4
0.4.3 3 / 4
0.4.2 3 / 4
0.4.1 3 / 4
0.4.0 3 / 4
0.3.9 3 / 4
0.3.8 3 / 4
0.3.7 3 / 4
0.3.6 3 / 4
0.3.5 3 / 4
0.3.4 3 / 4
0.3.3 3 / 4
0.3.2 3 / 4
0.3.1 3 / 4
0.3.0 3 / 4
0.2.35 3 / 4
0.2.34 3 / 4
0.2.33 3 / 4
0.2.32 3 / 4
0.2.31 3 / 4
0.2.30 3 / 4
0.2.29 3 / 4
0.2.28 3 / 4
0.2.27 3 / 4
0.2.26 3 / 4
0.2.25 3 / 4
0.2.24 3 / 4
0.2.23 3 / 4
0.2.22 3 / 4
0.2.21 3 / 4
0.2.20 3 / 4
0.2.19 3 / 4
0.2.18 3 / 4
0.2.17 3 / 4
0.2.16 3 / 4
0.2.15 3 / 4
0.2.14 3 / 4
0.2.13 3 / 4
0.2.12 3 / 4
0.2.11 3 / 4
0.2.10 3 / 4
0.2.9 3 / 4
0.2.8 3 / 4
0.2.7 3 / 4
0.2.6 3 / 4
0.2.5 3 / 4
0.2.4 3 / 4
0.2.2 3 / 4
0.2.1 3 / 4
0.1.14 3 / 4
0.1.13 3 / 4
0.1.12 3 / 4
0.1.11 3 / 4
0.1.10 3 / 4
0.1.9 3 / 4
0.1.8 3 / 4
0.1.7 3 / 4
0.1.6 3 / 4
0.1.5 3 / 4
0.1.4 3 / 4
0.1.3 3 / 4
0.1.2 3 / 4
0.1.1 3 / 4
0.1.0 3 / 4
0.0.3 3 / 4
0.0.2 3 / 4

v0.4.4

1 finding
INFO No provenance attestation provenance

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

v0.4.3

1 finding
INFO No provenance attestation provenance

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

v0.4.2

1 finding
INFO No provenance attestation provenance

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

v0.4.1

1 finding
INFO No provenance attestation provenance

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

v0.4.0

1 finding
INFO No provenance attestation provenance

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

v0.3.9

1 finding
INFO No provenance attestation provenance

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

v0.3.8

1 finding
INFO No provenance attestation provenance

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

v0.3.7

1 finding
INFO No provenance attestation provenance

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

v0.3.6

1 finding
INFO No provenance attestation provenance

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

v0.3.5

1 finding
INFO No provenance attestation provenance

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

v0.3.4

1 finding
INFO No provenance attestation provenance

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

v0.3.3

1 finding
INFO No provenance attestation provenance

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

v0.3.2

1 finding
INFO No provenance attestation provenance

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