← Home

@checkstack/healthcheck-dns-backend

51
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
provenance missing-githead AI (provenance): Internal scoped org package; missing gitHead is a CI environment change, not a malware indicator for this package. ai
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 consistent across all versions. ai
bogus-package bogus-package AI (bogus-package): Private @checkstack scoped package; missing metadata is consistent across the whole package family, not a spam indicator. ai
provenance no-provenance AI (provenance): Consistent across all @checkstack packages; not a risk indicator for this org. ai

Versions (showing 51 of 68)

View all versions
Version Deps Published
0.5.4 3 / 4
0.5.3 3 / 4
0.5.2 3 / 4
0.5.1 3 / 4
0.5.0 3 / 4
0.4.9 3 / 4
0.4.8 3 / 4
0.4.7 3 / 4
0.4.6 3 / 4
0.4.5 3 / 4
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.11 3 / 4
0.3.10 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.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.3 3 / 4
0.2.2 3 / 4
0.2.1 3 / 4
0.2.0 3 / 4

v0.5.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.5.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.5.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.5.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.5.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.4.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.4.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.4.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.4.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.4.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.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.