In any case, "a random nickname on the Internet, using a computer somewhere in the globe" is a lot more information than none.
Finding out that that's the case for a given project is part of traceability.
That information is meaningless if traces back to an empty room.
It's not perfect but it's something vs nothing. I'll take something every time.
You don't get commit rights as a random person, so yes, a commit can usually be traced back to a person. Sure, the committer could have received a patch from a unknown person, but then he's still responsible for the commit.
Any serious project would have some form of web of trust and know who has commit rights. It's up to you to decide if you trust their web of trust.
I guess from your comments that you are not actually interested in contributing to the discussion since you just sprout single line comments with no information at all.
Even if there is no direct audit of the code, once a vulnerability is discovered it can be traced back to the person(s) who introduced it.
With a closed system, only the owner of the source code history can do that. With open source, any person in the world can, and can start a discussion to understand whether it was malicious or not, if the person(s) should be banned from pushing code, new code security standards to be adopted, etc. You lean on the world's expertise at that point.
Bad things happen. It's important to have the ability to understand why and mitigate for the future.