Analytics

Releases in the last 12 months, with each tool's typical gap between releases. Almost entirely open source — commercial platforms ship continuously and rarely publish GitHub releases, so 507 of the 508 tools here are open-source.

How well each tool documents what it ships. Every release note is scored on depth, usage examples and transparency (breaking changes, advisories); a tool is scored on its median note out of its recent ones, so the three parts of each bar always add up to its total. Each tool is judged on the best channel it publishes in — the release itself, a CHANGELOG in the repo, or a changelog page — so a project isn't penalised for keeping its notes somewhere other than the release.

Incomplete. 231 tracked tools score nothing at all, because we haven't found where they document releases yet. A tool can jump from “worst” to mid-pack the day we find its changelog page, so read the ranking as indicative rather than settled.

Monthly releases per category over five years. A category climbing means more people are actively shipping that kind of tool; a flat line means the problem is either solved or abandoned.

How long tools stay in active development — average span (start → last activity), open-source vs commercial.

Incomplete. Commercial start dates come from a fallback chain ending in a hand-curated launch year, not repo history, so the commercial bars carry considerably more uncertainty than the open-source ones beside them.

Share of note-bearing releases whose text matches each theme, per quarter.

Maintenance activity of tracked tools (same thresholds as the tools page), and when tools first appeared.

Each category's release volume last quarter against its own trailing four-quarter median — a ratio, so a big category can't out-rank a small one on size alone. Above 1× is accelerating; below is cooling.

Projects that had a steady release rhythm and have since stopped — each measured against its own cadence, not a fixed threshold, so an annual release cycle isn't mistaken for silence. Most recently gone quiet first. This is not a judgement about a project or its maintainers: a finished tool legitimately stops shipping, and a repo can be actively developed without cutting releases. Read the cadence and the gap together, and check the repo before drawing a conclusion.