> there is no ...reliable way to verify the identity of a creator's SSH key
GitHub exposes your public key via it's API. (Why? I have no idea. I call it a privacy violation)
So, you need to create new github identity for every SSH identity that you wish to remain anonymous for, otherwise they just get tied together & one aspect of anonymity is lost.
All that does is associate an arbitrary SSH key with a GitHub account. There is still no reliable way to verify the identity of the GitHub account owner, or the SSH key that account holder generated.
How does that expose any more information than you do by pushing a commit with a GitHub account?
GitHub exposes your public key via it's API. (Why? I have no idea. I call it a privacy violation) So, you need to create new github identity for every SSH identity that you wish to remain anonymous for, otherwise they just get tied together & one aspect of anonymity is lost.