You can't vet the people, but you can vet the code. Of course, if you just give someone commit rights, then you can't. But generally speaking the maintainer understands the code they merge into a project, and that is the vetting that takes place.
Nobody's saying you should never accept a patch from an unknown person. "Of course, if you just give someone commit rights, then you can't." is the whole point!
If you're using auto-updating external packages, aren't you effectively giving the package author commit access to your derivative project too?
Sure, but then they have to actively invest time into the project... not everyone can afford that.
Then mark the project as abandoned and add a note suggesting the new volunteer’s fork.