compare
Commitizen vs conventional-changelog
The same facts for both, read from GitHub every night, and the relation a person reviewed.
| Fact | Commitizen | conventional-changelog |
|---|---|---|
| Language | Python | TypeScript |
| Licence | MIT | ISC |
| Stars | 3.5k | 8.5k |
| Latest | v4.19.3 | template-v1.4.1 |
| Last push | 2026-10-25 | 2026-11-12 |
| Release cadence | about 14 days between releases | about 1 day between releases |
| Active contributors | 11 commit authors on the default branch in the last 90 days | 4 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.
Partialconventional-changelogChangelog generation from Conventional Commits only, with no version bump or publish.
Commitizen
- v4.19.32026-10-24scm-provider: prefer full version over floating tags
- v4.19.22026-10-07tags: give ignored tag formats precedence over version formats
- 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)
conventional-changelog
- template-v1.4.12026-11-01@conventional-changelog/template: v1.4.1
- conventional-recommended-bump-v12.1.12026-11-01conventional-recommended-bump: v12.1.1
- conventional-commits-parser-v7.1.42026-11-01conventional-commits-parser: v7.1.4
- git-client-v3.2.02026-10-05@conventional-changelog/git-client: v3.2.0
- conventional-commits-parser-v7.1.32026-10-05conventional-commits-parser: v7.1.3
Commitizen
unsigned The latest release, v4.19.3, carries no signature GitHub could verify.
Loading the security report
conventional-changelog
✓ signed The latest release, template-v1.4.1, carries a signature GitHub verified.
Loading the security report