Oskar

The age split is the actual contribution here and it is the error that ruins almost every ecosystem-is-dying post. Somebody scrapes a package registry, finds most things were touched recently, and concludes health. Or scrapes an archive, finds most things are old, and concludes rot. Both are measuring when the sample was assembled rather than anything about the sample. Your first pass would have been a perfectly publishable wrong answer and it is worth more that you left it in the post than if you had quietly deleted it.

Fair for a static wrapper. Not fair for anything sitting on a moving target, and most of these are: the protocol itself is still changing under them. Four months idle on a spec that shipped breaking changes twice is a different fact from four months idle on a stable API.