← Home

@commitlint/load

npm Repository Homepage
14
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

marioneblmartinhelmutescapedcatbycedric

Keywords

commitlintconventional-changelogcorelibrary

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:koa AI (typosquat): @commitlint/load is a scoped package in the well-known commitlint monorepo; Levenshtein comparison to 'koa' is a false positive for scoped packages. ai
typosquat typosquat.levenshtein:zod AI (typosquat): @commitlint/load is a scoped package in the well-known commitlint monorepo; Levenshtein comparison to 'zod' is a false positive for scoped packages. ai
semgrep semgrep:dynamic-require AI (semgrep): Dynamic require is used to read the 'version' field from a resolved package.json path — standard metadata inspection, not arbitrary code execution. ai

Versions (showing 14 of 14)

Version Deps Published
21.0.2 9 / 5
21.0.1 9 / 5
21.0.0 9 / 4
20.5.3 9 / 4
20.5.2 9 / 5
20.5.0 9 / 5
20.4.4 9 / 5
20.4.3 9 / 5
20.4.0 9 / 5
20.3.1 10 / 7
20.3.0 10 / 7
20.2.0 10 / 7
20.1.0 10 / 7
20.0.0 10 / 7

v21.0.2

1 finding
LOW No provenance attestation provenance

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

v21.0.1

1 finding
LOW No provenance attestation provenance

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

v21.0.0

1 finding
LOW No provenance attestation provenance

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

v20.5.3

1 finding
LOW No provenance attestation provenance

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

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

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

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