https://github.com/vuca-dev/unstale

I built unstale it because I found no other tools that could proactively track & inform me during development of all the new updates & shipped features in my stack (which is tough to keep up with on my own, with how fast most teams are shipping nowadays).

In comparison, other tools are - either strictly dedicated to security advisories, or dependabot-style bumps (unstale informs on both of those, plus breaking changes, plus new features) - a docs MCP or equivalent, which requires human or agent to search in a somewhat brute force fashion, and without knowing what they're looking for (unstale proactively crawls docs and announcement pages, then filters and surfaces a tight brief through a skill file)

The single metric that I think best demonstrates being worth people's time (and that it works) is that on a 19-repo test, unstale found 4x the impactful updates (hand scored by me - not just nits) at 1/16th the token spend of claude code on its own. Eval framework is also included in the repo, for people's scrutiny.

I'm excited at this point to hear from others:

1) Is keeping up with new releases in your stack a shared struggle 2) If yes, are there other ways people are or would solve it? 3) Pressure testing my own design choices for the tool against a wider community. (Skill file as the appropriate delivery method vs hooks vs MCP? DX like temperament & sensitivity threshold on what changes are worth surfacing? And other questions that I'm sure people much smarter than me will raise :) )

Access is easy - you can use it for free with a single npx install command in your working repo of choice.