← Home

@commitlint/cli

npm Repository Homepage
16
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

clicommitlintconventional-changelog

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:joi AI (typosquat): @commitlint/cli is a well-known scoped package with 3200+ days of history; Levenshtein match to 'joi' is a clear false positive with no impersonation intent. ai
phantom-deps phantom-dep:@commitlint/types AI (phantom-deps): Same-org sibling package used for types; not directly imported in entry point but legitimately declared. Stable pattern for this monorepo. ai
phantom-deps phantom-dep:@commitlint/format AI (phantom-deps): Same-org sibling package; phantom-dep finding is a stable false positive for this monorepo's dependency structure. ai

Versions (showing 16 of 16)

Version Deps Published
21.0.2 7 / 6
21.0.1 7 / 6
21.0.0 7 / 6
20.5.3 7 / 7
20.5.2 7 / 8
20.5.0 7 / 8
20.4.4 7 / 8
20.4.3 7 / 8
20.4.2 7 / 7
20.4.1 7 / 7
20.4.0 7 / 7
20.3.1 7 / 7
20.3.0 7 / 7
20.2.0 7 / 7
20.1.0 7 / 7
20.0.0 7 / 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.5.0

1 finding
LOW No provenance attestation provenance

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

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.