💅 Beautiful Changelogs using Conventional Commits
1.3k
Stars
73
Forks
100
Open issues
30
Contributors
AI Analysis
Changelogen generates formatted changelogs from Conventional Commits with integrated semver versioning, git tagging, and npm publishing. It's specifically designed for JavaScript/Node.js projects that follow conventional commit conventions and need automated release workflows. Best suited for open-source library maintainers and teams managing monorepos or multiple package releases.
Inferred from signals mentioned in the README (tests, CI, type safety) — not a review of the actual code.
AI's overall editorial judgment — not an average of the bars above, can weigh other factors too.
Lightweight conventional-commit changelog generator with integrated versioning and GitHub release sync
Changelogen is a TypeScript-based CLI tool that generates formatted changelogs from git commit histories following Conventional Commits, with integrated semver bumping and GitHub release management. Built by unjs (a Node.js utilities collective), it targets JavaScript/TypeScript projects seeking automation for release workflows. Real-world adoption appears concentrated within the unjs ecosystem itself; broader adoption remains unverified.
Created in May 2022, changelogen emerged as the unjs organization's answer to changelog automation. It appears designed to serve as an opinionated, lighter alternative to the more established conventional-changelog ecosystem while maintaining integration with modern release tooling.
Star count has grown modestly to 1,252 over ~4 years, with minimal recent momentum (1 star in last 7 days as of July 2026). Growth appears tied to adoption within the unjs ecosystem rather than broader JavaScript community adoption. Forks (73) and download metrics suggest a stable but niche user base.
Adoption not verified in README or metadata. No explicit case studies, production user testimonials, or download statistics provided. Some signal from unjs ecosystem visibility (organization with multiple projects), but concrete production adoption claims absent. NPM download badge exists but actual numbers not documented.
Based on README, likely implements a conventional-commit parser that extracts commit metadata, organizes by type (feat/fix/breaking), generates formatted markdown, and interfaces with git and npm CLI tools. Appears to delegate version bumping to semver logic and GitHub API interaction to a GitHub subcommand. Exact parsing strategy and architecture not verifiable from README alone.
README mentions codecov badge and references interactive tests via 'pnpm dev', but specific coverage percentage or test count not documented. Presence of codecov integration suggests automated test infrastructure exists.
Last commit 2026-06-26 (8 days before analysis date) indicates active maintenance. TypeScript codebase with modern tooling (pnpm, corepack) implies sustained development practices. However, issue velocity and PR response time not available from metadata alone.
ADOPT IF: you are already invested in the unjs ecosystem or strongly prefer opinionated, zero-config changelog tooling with integrated GitHub release sync for a Node.js project using conventional commits. AVOID IF: you require extensive customization, templating, or ecosystem-wide tool integration — conventional-changelog ecosystem offers richer plugin landscape. MONITOR IF: you need changelog automation but aren't yet committed to a solution; mainstream adoption signals remain weak, which may indicate early-stage stability concerns or simply confirmed niche positioning.
Independent dimensions
Mainstream potential
3/10
Technical importance
6/10
Adoption evidence
2/10
- Adoption not independently verified; strong dependence on unjs ecosystem for real-world use cases suggests risk of becoming orphaned if org focus shifts.
- Compared to conventional-changelog (8.4k stars, 20+ years history), smaller community means fewer third-party plugins and integrations; customization may require forking.
- GitHub release sync feature appears relatively recent; may contain edge cases not yet surfaced in production at scale.
- Minimal recent star growth and low activity (1 star/week) suggest limited momentum outside existing user base; future maintainability depends on unjs commitment.
- No documented migration path from conventional-changelog or standard-version; switching costs non-zero for established projects.
Likely to remain a stable, niche tool within the unjs ecosystem and projects that adopt it early. Low probability of mainstream adoption unless significant marketing push or viral adoption event occurs. Most probable trajectory: maintains steady maintenance, slow organic growth, persistence as "smaller alternative for teams already using unjs".
Newsletter
Get analyses like this every Monday
Free weekly digest of the most interesting open-source discoveries.
Languages
Information
- Language
- TypeScript
- License
- MIT
- Last updated
- 2w ago
- Created
- 51mo ago
- Analyzed with
- anthropic/claude-haiku-4-5
Stars over time
Contributors over time
Top 100 contributors only — repos with more will plateau at 100.
Open issues
Recent releases
Similar repos
conventional-changelog/conventional-changelog
Conventional Changelog generates changelogs and release notes automatically...
vercel/release
Release is a CLI tool that automatically generates GitHub releases and...
conventional-changelog/standard-version
Standard-version is a CLI tool for automating semantic versioning and CHANGELOG...
cookpete/auto-changelog
auto-changelog is a command-line tool that generates formatted changelogs from...
| Repository | Stars | Week Δ | Language | Score | Updated |
|---|---|---|---|---|---|
|
|
1.3k | — | TypeScript | 8/10 | 2w ago |
|
|
8.5k | — | TypeScript | 8/10 | 14h ago |
|
|
3.6k | — | JavaScript | 8/10 | 2mo ago |
|
|
8k | — | JavaScript | 6/10 | 3w ago |
|
|
1.4k | — | JavaScript | 7/10 | 1mo ago |
|
|
18.6k | — | TypeScript | 8/10 | 21h ago |
Mature, ecosystem standard with broader plugin architecture and longer maintenance history. Changelogen likely offers simpler, more opinionated workflow but narrower customization surface.
Established semantic versioning tool with similar changelog + bumping integration. Changelogen appears functionally comparable but with potentially lighter footprint and fewer adoption signals.
Similar star range but different philosophy (auto-parsing without strict conventional commits). Changelogen enforces structured commit format; auto-changelog more lenient.
More recent, from high-profile org, but narrower scope. Changelogen broader (changelog + version + publish). Direct comparison limited by different design intent.