olivierlacan/keep-a-changelog

If you build software, keep a changelog.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 24 minutes ago
Added to GitGenius on September 9th, 2026
Created on May 31st, 2014
Open Issues & Pull Requests: 43 (+0)
GitHub issues: Enabled
Number of forks: 3,541
Total Stargazers: 6,697 (+0)
Total Subscribers: 95 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 20.8 days
Mean response time: 68.7 days
90th percentile: 179.4 days
Tracked items: 21

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 100% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Only 8% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 20
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 625 days
Stale 30+ days: 19
Stale 90+ days: 16

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • enhancement (1)
  • wontfix (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Keep a Changelog is a specification and website that defines a standard format for maintaining software changelogs.

The project addresses the problem of inconsistent, poorly maintained changelogs by establishing a convention for how to structure and present release notes. It provides a clear specification that separates changes into categories like Added, Changed, Deprecated, Removed, Fixed, and Security, organized by version. The approach is straightforward: adopt the format described on the keepachangelog.com website and apply it consistently to your project's changelog file.

Teams should adopt this specification if they want their release notes to be predictable and easy for users to scan. It works well for any software project that makes releases and wants to communicate changes clearly to its audience. The format is language-agnostic and works equally well for libraries, applications, and tools. The specification is simple enough that it requires no tooling beyond a text editor, making it accessible to projects of any size or complexity.

The project maintains an active contribution workflow with documented development setup and translation processes in its contributing guide, indicating ongoing engagement with the community. The repository welcomes issues and pull requests, suggesting responsiveness to feedback and improvements from users.