Or worse: find out you need a security fix and that a large dependency chain is more than one major version behind. The issue is publically known and easy to scan for. The clock is ticking...
if upgrading is that bad can always (usually) patch it yourself
Have we sunk that low that the idea of using mature, stable and supported libraries is idealistic and paranoid now? It used to just be called responsible.
> but that's just not how majority of developers work, so it's a bit of a moot point
I don't think identifying the root cause of an issue is ever a moot point.