It's not irrelevant. When a community project depends on another project, it depends on it, (both factually and tautologically.) If the original maintainer evap

It's not irrelevant. When a community project depends on another project, it depends on it, (both factually and tautologically.) If the original maintainer evaporates, the community project needs to adapt by either moving somewhere else or forking away and adopting the project. Else the community is in a broken state, all other expectations aside! That's not to say the original author owes any debt to the community, but when pay is the only motivation you wind up with chronically broken communities optimized for rent extraction. (And I'm definitely not saying that OSS authors shouldn't be paid either...) authors can walk away from their creations, but it doesn't make the result of doing that without any concern any less important or relevant here. You're not really suggesting that OP's concerns are somehow irrelevant because code owners need to be protected from bad actors by annoying/bugged-out or broken gatekeeping robots, are you?