commitizen
2
Versions
—
License
No
Install Scripts
Verified
Provenance
Supply chain provenance
Status for the latest visible version.
SLSA provenance attestation
npm registry signatures
gitHead linked
Maintainers
linusukentcdoddsjimthedevcommitizen-botpgoodjohn
Keywords
commitprettyformatconventional changelogcommitizen
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from bot account to GitHub Actions CI/CD with SLSA provenance; legitimate automation change. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Mature package with infrequent releases; dormancy is normal for stable tooling. | ai | |
| phantom-deps | phantom-dep:cz-conventional-changelog | AI (phantom-deps): cz-conventional-changelog is intentionally referenced via config (not require) as commitizen's default adapter. This is by design and stable across versions. | ai | |
| dependencies | unvetted-dep:cz-conventional-changelog | AI (dependencies): cz-conventional-changelog is the canonical commitizen adapter and a legitimate, well-known dependency for this package. | ai |
v4.3.2
2 findings
HIGH
Publisher changed: commitizen-bot → GitHub Actions (on 2026-06-12)
provenance
This version was published by a different npm account than previous versions on 2026-06-12. This could indicate a legitimate maintainer transition or an account compromise.
INFO
Has SLSA provenance attestation
provenance
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.3.1
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.