unjs

unjs/changelogen

TypeScript MIT Dev Tools high-open-issues

💅 Beautiful Changelogs using Conventional Commits

1.3k stars
73 forks
recent
GitHub

1.3k

Stars

73

Forks

100

Open issues

30

Contributors

v0.6.2 06 Jul 2025

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.

Dev Tools Developer Tool Discovery value: 5/10
Documentation 8/10
Activity 9/10
Community 7/10
Code quality 7/10

Inferred from signals mentioned in the README (tests, CI, type safety) — not a review of the actual code.

Overall score 8/10

AI's overall editorial judgment — not an average of the bars above, can weigh other factors too.

changelog-generation conventional-commits release-automation semver npm-publishing
Actively maintained MIT licensed Niche/specialized use case Production ready
Deep Analysis · Based on README and public signals
6d ago

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.

Origin

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.

Growth

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.

In production

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.

Code analysis
Architecture

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.

Tests

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.

Maintenance

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.

Honest verdict

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

Risks
  • 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.
Prediction

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".

0 found this helpful

Newsletter

Get analyses like this every Monday

Free weekly digest of the most interesting open-source discoveries.

Languages

TypeScript
98.5%
JavaScript
1.5%

Information

Language
TypeScript
License
MIT
Last updated
2w ago
Created
51mo ago
Analyzed with
anthropic/claude-haiku-4-5

Stars over time

Loading…

Contributors over time

Top 100 contributors only — repos with more will plateau at 100.

Loading…

Similar repos

conventional-changelog

conventional-changelog/conventional-changelog

Conventional Changelog generates changelogs and release notes automatically...

8.5k TypeScript Dev Tools
vercel

vercel/release

Release is a CLI tool that automatically generates GitHub releases and...

3.6k JavaScript
conventional-changelog

conventional-changelog/standard-version

Standard-version is a CLI tool for automating semantic versioning and CHANGELOG...

8k JavaScript Dev Tools
cookpete

cookpete/auto-changelog

auto-changelog is a command-line tool that generates formatted changelogs from...

1.4k JavaScript Dev Tools
conventional-changelog

conventional-changelog/commitlint

commitlint is a linter for commit messages that enforces the conventional...

18.6k TypeScript Dev Tools
vs. alternatives
conventional-changelog (8,472 stars)

Mature, ecosystem standard with broader plugin architecture and longer maintenance history. Changelogen likely offers simpler, more opinionated workflow but narrower customization surface.

standard-version (7,973 stars)

Established semantic versioning tool with similar changelog + bumping integration. Changelogen appears functionally comparable but with potentially lighter footprint and fewer adoption signals.

cookpete/auto-changelog (1,387 stars)

Similar star range but different philosophy (auto-parsing without strict conventional commits). Changelogen enforces structured commit format; auto-changelog more lenient.

vercel/release (3,584 stars)

More recent, from high-profile org, but narrower scope. Changelogen broader (changelog + version + publish). Direct comparison limited by different design intent.