Community-driven stability verdicts for npm packages. Because
latestdoesn't meangreatest.
IsItStable answers one question: "Should I update?"
Every tracked package version gets a community verdict — YES ✅ (ship it) or NO 🔥 (hold off). Verdicts are backed by evidence: referenced GitHub issues, download stats, and community votes via GitHub reactions.
- Version issues are created in this repo with the format
[v2026.4.23] PackageName - Each issue contains a verdict (YES/NO), humorous comment, and evidence links
- You vote by reacting on the issue: 👍 = stable, 👎 = unstable
- The website reads from GitHub Issues via API — no database needed
All endpoints return JSON with Cache-Control headers.
Latest verdict for a package.
{
"package": "openclaw",
"version": "2026.4.23",
"verdict": "yes",
"comment": "Ship it and sleep like a baby.",
"thumbsUp": 12,
"thumbsDown": 1
}All tracked versions for a package.
Latest version with a YES verdict. Includes an install command.
Detailed info for a specific version including referenced issues and stats.
Open an issue requesting the package you want tracked.
pnpm install
pnpm devOptionally set GITHUB_TOKEN in .env.local for higher API rate limits:
GITHUB_TOKEN=ghp_...
- Next.js — React framework with SSG + ISR
- Vercel — Hosting & edge caching
- GitHub API — Issues as database, reactions as votes
- Tailwind CSS — Styling
- Fork this repo
- Create a feature branch
- Submit a PR
For version verdicts, open an issue instead.
If this saves you from a bad npm update, consider sponsoring 💛
MIT