He didn't set out to maintain the library for two decades. He wrote it as a side project, other developers started depending on it, and at some point stepping away stopped feeling like an option.
The library itself is unglamorous — a small utility buried three or four dependencies deep in projects most of its users have never heard of by name. But enough software quietly imports it that a serious bug would ripple further than almost anyone realizes.
The job nobody applies for
He's tried twice to hand the project to someone else. Both times, the volunteers underestimated how much unpaid, unglamorous work maintenance actually is — patching security issues, triaging bug reports, saying no to feature requests that would break something else.
He keeps doing it anyway, largely because he's watched what happens when a widely used library loses its maintainer: forks multiply, security patches lag, and the ecosystem quietly gets worse in ways most users never trace back to the source.