Something else to think about @cymplecy is when the author of the contrib node simply stops responding regardless of personal situation. I can see that happening towards myself if my health further worsens. It wouldn’t just be ownership of a repository, but once packages are registered to npm that name is registered too, and only the original owner can transfer the ownership for that.
A result of that would be (numerous) forked nodes that get published on their own package. It already happens like that, try searching the flows library for “elasticsearch”, they all have the same original contrib node. It makes searching for nodes from the palette even harder as you can’t see the real difference between all of them without checking out the source code.
The idea definitely has merit, but don’t forget about the difficulties it might/can get also deal with ownership towards the OpenJS Foundation, as that what’s moving to the node-red organisation would likely mean as well. Even just forking would make it difficult I believe. But food for thought for sure