compare
Commitizen vs git-cliff
The same facts for both, read from GitHub every night, and the relation a person reviewed.
| Fact | Commitizen | git-cliff |
|---|---|---|
| Language | Python | Rust |
| Licence | MIT | Apache-2.0 |
| Stars | 3.5k | 12k |
| Latest | v4.19.1 | v2.14.2 |
| Last push | 2026-10-06 | 2026-09-18 |
| Release cadence | about 15 days between releases | about 56 days between releases |
| Active contributors | 9 commit authors on the default branch in the last 90 days | 23 commit authors on the default branch in the last 90 days |
| Flags | none | none |
How they relate
Both replace semantic-release. Alternatives to semantic-release →
PartialCommitizenBumps the version, writes the changelog and tags from conventional commits, but does not publish packages or releases.
Partialgit-cliffChangelog generation only, no version bump or publish.
Commitizen
- v4.19.12026-10-03bump: use VersionIncrement ordering for bump detection (#2097)
- v4.19.02026-09-22add extensible commit filters
- v4.18.02026-08-19commit: add a tag(--body-length-limit) and a function for command commit (#1849)
- v4.17.12026-08-17init: skip hook question when no installer is present
- v4.17.02026-07-29cmd/version: add support for --next USE_GIT_COMMITS
Commitizen
unsigned The latest release, v4.19.1, carries no signature GitHub could verify.
Loading the security report
git-cliff
✓ signed The latest release, v2.14.2, carries a signature GitHub verified.
Loading the security report