Lint report — php-src

A

92/100 — Excellent. 60 entries checked against 7 practices from the Wakelog guides.

Nothing was saved. Lint another · how the big projects score · preview it as a hosted page

Checks

PASS
Recognizable release entries. 60 entries parsed ("## heading" style). Guide: The Keep a Changelog format, explained
PASS
Every entry has a date. All entries carry a date — readers can tell when things shipped. Guide: The Keep a Changelog format, explained
WARN
Newest release first. 4 entries are out of date order. Guide: Changelog page design: layout and UI patterns that work
PASS
Titles say what changed. No “bug fixes and improvements”-style filler titles found. Guide: How to write a changelog (with examples)
PASS
Entries have content. No empty version-only entries. Guide: Release notes templates: copy-paste formats for every kind of change
PASS
Written for readers, not a commit dump. Entries read like notes for humans, not raw git log. Guide: Generate a changelog from git commits (without publishing garbage)
NOTE
Breaking changes stand out. No breaking changes mentioned. When one ships, flag it loudly — “Breaking:” first, migration steps included. Guide: How to announce breaking changes (without losing users)

Put the grade in your README changelog grade A badge

A live badge that re-grades this URL daily and links back to the full report:

[![changelog grade](https://wakelog.wakelog.workers.dev/lint/badge.svg?url=https%3A%2F%2Fgithub.com%2Fphp%2Fphp-src)](https://wakelog.wakelog.workers.dev/lint?url=https%3A%2F%2Fgithub.com%2Fphp%2Fphp-src)

Different label? Tune it in the badge playground.

Want a changelog that passes by construction? Host it on Wakelog — free, 30-second signup, no email. Import this exact file in one paste (dates preserved), get a public page with permalinks, RSS, a widget and an API. Not convinced? See how it would look first.