orhun/git-cliff

This system is git-cliff, a changelog generation tool that parses git commit history to produce structured release notes. It operates as both a command-line interface and a reusable core library, supporting integration with multiple remote platforms like GitHub, GitLab, and Bitbucket. The project includes comprehensive tooling for packaging, documentation, and testing to facilitate its distribution and maintenance.

7 changes.

The project was initialized with comprehensive configuration, including Nix support and documentation, while replacing placeholder code with a robust changelog generation engine. The architecture was restructured into a core library and CLI binary, featuring a major overhaul of the command-line interface and the implementation of integration tests for end-to-end validation.

9 changes.

The project expanded its core functionality by adding support for Azure DevOps, Bitbucket, Gitea, and GitLab remotes, while also introducing an npm package with a TypeScript API. Concurrently, the documentation website was rebuilt using Docusaurus v3 with a dark theme, enhanced with user testimonials, analytics, and end-to-end testing.

A new \package.json.tmpl\ file has been added to the npm directory, defining the metadata structure for the npm distribution of git-cliff. This template specifies the package name, version, description, repository URL, and keywords, while also configuring the license as MIT OR Apache-2.0 and setting the publish configuration to public access. This change enables the packaging and publishing of git-cliff as an npm package.

npm · high confidence

A new \.well-known/funding-manifest-urls\ file has been added to the repository root, pointing to \https://orhun.dev/funding.json\. This allows external tools and users to discover the project's funding information via the standard well-known URI path.

.well-known · high confidence

The changelog generation logic has been moved into the git-cliff-core library, making it available as a reusable library API. This change introduces the core changelog generation components (Changelog, CommitProcessor, Release) and their associated configuration and processing modules within the core crate, enabling other tools and applications to integrate changelog generation functionality directly.

git-cliff-core/src · high confidence

The repository is initialized with core configuration files including \cliff.toml\ for changelog generation, a \Dockerfile\ for containerized builds, and a \release.sh\ script to automate versioning and publishing. Support for Nix-based development and builds is added via \flake.nix\ and \flake.lock\, while documentation standards are established with \CONTRIBUTING.md\ and \SECURITY.md\.

(repo-wide) · high confidence

The npm package now uses Yarn 4.1.0 (with the release binary committed to .yarn/releases) and provides a programmatic API for TypeScript consumers. This includes a new \skipCommit\ option that accepts an array of values, alongside several fixes for binary path resolution, type casting, and Windows binary naming.

npm/git-cliff · high confidence

The website now displays a new 'HomepageFeatures' section highlighting git-cliff's key capabilities, including its regex-powered custom parsers, support for conventional commits, and easy integration as a CLI tool or library. Additionally, a 'Testimonials' component has been added to the homepage, which randomly displays user feedback from notable figures and organizations like GitHub and Greptime Database, complete with links to their original posts.

website/src/components · high confidence

Users can now fetch commit and pull request metadata from Azure DevOps, Bitbucket, Gitea, and GitLab in addition to the existing GitHub support. This change introduces dedicated client implementations for each provider in the remote module, enabling the tool to integrate with these platforms for changelog generation.

git-cliff-core/src/remote · high confidence

The website now includes a dedicated landing page for the 10,000 stars giveaway, featuring a Gleam widget and links to the merchandise store. A new redirect page has been added to route users to the GitHub issue template, and a site.webmanifest file has been introduced to support Android Chrome browser icons.

website/static · high confidence

The default main.rs file containing a simple "Hello, world!" print statement has been removed from the gitolith-cli package. This indicates the CLI application is no longer using this basic stub as its entry point, likely as part of the broader refactoring to implement the actual changelog generation features.

gitolith-cli · high confidence

The website's home page has been updated to include a new visual design featuring an animated Git-Cliff GIF in the hero banner, a custom font, and a dedicated section for user testimonials. Additionally, the page now integrates Umami analytics tracking via a script in the head section.

website/src/pages · high confidence

The website has been rebuilt using Docusaurus v3, upgrading from the previous v2 version. This change introduces a new default dark theme for the site, adds a local search bar via the @easyops-cn/docusaurus-search-local plugin, and includes social links for GitHub, Discord, Mastodon, and Twitter in the navigation and footer. The configuration also standardizes on Yarn for dependency management and includes Playwright for end-to-end testing.

website · high confidence

This release introduces a significant behavioral change by restructuring the application into a core library and a new binary crate, which alters the internal API and module organization. The command-line interface has been completely redesigned using clap v4, introducing new argument structures, environment variable prefixes (GIT\CLIFF\), and refined help styling. Key user-facing features include improved configuration file discovery (supporting project-local and user directories), the ability to initialize configs with custom or built-in templates, and enhanced changelog generation capabilities such as commit statistics, sorting options, and support for multiple repositories and submodules. The logging system has been migrated to the tracing ecosystem with visual progress indicators, and performance profiling is now available via a feature flag.

git-cliff · high confidence

Added end-to-end test for crawling site console errors; Added integration tests for changelog generation; Removed placeholder unit test from gitolith-core.

The project has replaced the previous gitolith components with the git-cliff changelog generator, introducing new Cargo manifests for git-cliff-core and the git-cliff CLI. The Rust edition has been upgraded to 2024, raising the minimum supported Rust version (MSRV) to 1.88.0. Core dependencies have been updated, including clap to 4.6.6, serde to 1.0.229, and git2 to 0.21, while the npm and website packages have been refreshed to align with these changes.

(dependencies) · high confidence

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

• CAI 68 → 69 (+1.3)
• Rubric changed (rubric-2026.09.8 → rubric-2026.09.17) — scores are not directly comparable.

• Code Health 89 → 89 (+0.0)
• Architecture 100 → 98 (-2.2)
• Maturity 60 → 60 (-0.0)
• Readiness 70 → 67 (-3.1)
• Security 65 → 74 (+8.8)
• Domain Modelling 100 → 100 (+0.0)
• Performance 100 (new)

• Documentation: no installation or build instructions (README.md)
• Documentation: no project overview (README.md)
• Hotspot: git-cliff-core/src/release.rs (git-cliff-core/src/release.rs)
• Hotspot: git-cliff-core/src/template.rs (git-cliff-core/src/template.rs)
• Off-boarding risk: anonymized user #1

• Dependency hygiene PARTLY measured — Cargo dependencies read, dependency currency not (crates.io unreachable)
• Documentation: no usage examples (website/docs/index.md)
• Medium vulnerability: RUSTSEC-2026-0285 (Cargo.lock)
• Off-boarding risk: anonymized user #1
• Redundant initialization methods with unclear distinction. init_config likely uses default templates, while init_config_from uses a custom directory. The naming does not clearly convey that one is 'default' and the other is 'custom path'.

• 5 commits — 3 feature/other, 2 fixes

• git-cliff-core/src — 2 commits
• (root) — 1 commit
• .github/fixtures — 1 commit
• website/blog — 1 commit

• fix: fix(args): resolve --workdir to a repo-relative include path (#1369) (#1627)
• fix: fix(git): keep commits without file changes when only exclude_paths is set (#1637)
• change: chore(release): prepare for v2.14.2
• change: docs(website): add highlights for 2.14.2 (#1646)
• change: test(git): disable tag signing when running tests (#1641)

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

orhun/git-cliff was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point a surveyor at a repository you know and see whether you agree with it.