← Home

mailchecker

npm Repository Homepage
15
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

fgribreau

Keywords

emaildomainsdisposable

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:mu2 AI (dependencies): Longstanding template dep for build scripts, stable across versions. ai
dependencies unvetted-dep:node-range AI (dependencies): Small utility dep used in build tooling, stable across versions. ai
phantom-deps phantom-dep:mu2 AI (phantom-deps): Used only in build/config scripts, not runtime import. ai
phantom-deps phantom-dep:glob AI (phantom-deps): Used only in build/config scripts, not runtime import. ai
phantom-deps phantom-dep:async AI (phantom-deps): Used only in build/config scripts, not runtime import. ai
phantom-deps phantom-dep:lodash AI (phantom-deps): Used only in build/config scripts, not runtime import. ai
phantom-deps phantom-dep:eventemitter2 AI (phantom-deps): Used only in build/config scripts, not runtime import. ai

Versions (showing 15 of 15)

Version Deps Published
6.0.21 0 / 14
6.0.20 0 / 14
6.0.19 0 / 14
6.0.18 0 / 14
6.0.17 0 / 14
6.0.16 6 / 9
6.0.15 6 / 9
6.0.14 6 / 9
6.0.13 6 / 9
6.0.12 6 / 9
6.0.11 6 / 9
6.0.10 6 / 9
6.0.9 6 / 9
6.0.8 6 / 9
6.0.5 6 / 9

v6.0.21

1 finding
LOW No provenance attestation provenance

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

v6.0.17

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.

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

v6.0.15

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.

v6.0.14

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.

v6.0.13

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.

v6.0.12

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.

v6.0.11

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.

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

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

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

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