Lint report — neovim

C

68/100 — Needs work. 55 entries checked against 9 practices from the Wakelog guides.

Graded from: GitHub Releases API (55 releases). Repo-URL grades reflect whichever releases are visible right now and can vary between runs — lint the raw CHANGELOG.md URL for a stable grade.

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

Checks

PASS
Recognizable release entries. 55 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
PASS
Newest release first. Entries run newest to oldest. 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. 3 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)
WARN
Bullets say what changed. 3 of 1342 bullets carry no information (“wip”, “fix stuff”, “merged PR”). Say what changed and why a reader cares — or cut the line. Guide: How to write a changelog (with examples)
WARN
Breaking changes stand out. Breaking changes are mentioned mid-text but not flagged — lead with “Breaking:” or a heading so skimmers can’t miss them. Guide: How to announce breaking changes (without losing users)
WARN
Security fixes are actionable. 1 security-related entry with no affected versions or upgrade guidance. Say who’s affected and what to do — vagueness reads as cover-up. Guide: Security advisories vs changelog: how to publish a security fix

Specific entries to fix

  • NVIM v0.7.0 — Reads like raw commit output — rewrite for humans.
  • NVIM v0.6.1 — Reads like raw commit output — rewrite for humans.
  • NVIM v0.6.0 — Reads like raw commit output — rewrite for humans.
  • Nvim 0.10.3 — “Misc” says nothing — name the change or drop the bullet.
  • NVIM 0.10.1 — “Misc” says nothing — name the change or drop the bullet.
  • NVIM 0.3.8 — Security fix with no affected-versions or action guidance.

Put the grade in your README changelog grade C 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%2Fneovim%2Fneovim)](https://wakelog.wakelog.workers.dev/lint?url=https%3A%2F%2Fgithub.com%2Fneovim%2Fneovim)

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.