CHANGELOG.md (Keep a Changelog)
CHANGELOG.md is a community convention for a human-readable, Markdown- formatted file at the root of a project that records notable changes between versions. The leading specification is "Keep a Changelog" by Olivier Lacan, which defines a stable, opinionated set of section headings (Added, Changed, Deprecated, Removed, Fixed, Security) and recommends pairing with Semantic Versioning (SemVer). The format is widely adopted across open source and enterprise projects as the de facto way to document API and software releases in a way that is readable by humans and parseable by tooling.
Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.
API Evangelist profiles CHANGELOG.md (Keep a Changelog) the way a machine reads it — 25 machine-readable artifacts, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — CHANGELOG.md (Keep a Changelog) scores 10.6/100 (minimal), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile CHANGELOG.md (Keep a Changelog)
Each block below is one kind of artifact we hold for CHANGELOG.md (Keep a Changelog). For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
Features 15
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Markdown-Formatted
Human-Readable
Machine-Parseable
Semantic Sections
Semantic Versioning Alignment
Date-Stamped Releases
Unreleased Section
Added Section
Changed Section
Deprecated Section
Removed Section
Fixed Section
Security Section
Reverse Chronological Order
Release Comparison Links
Scroll within the panel for all 15 ·
Security Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Use Cases 9
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Open Source Project Release Notes
API Change Documentation
SDK Release Notes
Package Manager Metadata
Library Deprecation Tracking
Security Disclosure
Automated Release Tooling
Monorepo Component Changelogs
Regulatory / Compliance Change Records
Scroll within the panel for all 9 ·
Resources
Every other property we hold for CHANGELOG.md (Keep a Changelog) — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 4
Reference material describing how the API behaves
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Commercial 2
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/changelog-md · machine-readable index on apis.io