Lint report — TypeScript
B
84/100 — Good. 100 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. 100 entries parsed ("## heading" style) — capped at 100.
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. 8 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
WARN
Written for readers, not a commit dump. 2 entries look like raw git log output (commit hashes / “feat:” prefixes). Generated lists are a draft — edit before publishing.
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)
Specific entries to fix
- TypeScript 4.9.4 — Reads like raw commit output — rewrite for humans.
- TypeScript 4.9 — Reads like raw commit output — rewrite for humans.
Put the grade in your README

A live badge that re-grades this URL daily and links back to the full report:
[](https://wakelog.wakelog.workers.dev/lint?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2FTypeScript)
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.