Instead of a full "takeover", another possibility is to start a "Community Edition" with a transaparently managed repository. There the needed fix could be applied first, without ruling out the possibility of a return of the old main developer.
This sounds like a good idea to me.