Yes, this is another very bad example that I would never have used myself. It is entirely non-descriptive and when I look into the list of repo’s then it tells me nothing, so it is only hoping that a good description is given to it. These kinds of names are flaws of doing good PR and marketing.
There’s an example of a company that has common names for things that are both products and projects / technical components and that is Hashicorp. If you look at the names they chose you see that they don’t have direct clashes with technical terms in their own domain. So names like Vagrant, Terraform, Consul, etc. They also have ‘go-plugin’. Imagined they named that ‘Plugin’… boom, you’d never be able to find it without knowing more of the context it is applicable to.
People that are deeper involved into a project tend to speak the common terminology / slang naturally and in their short forms. With a name like ‘Proxy’ around, they also make toots such as “I just PR’ed [cool stuff] to #proxy”. And anyone reading and interested in [cool stuff] would be lost. There’s no googling of it, proxy is max. overloaded term.
If you wanted to follow a similar strategy to Hashicorp and choose a very comprehensive single word, then you might look in the thesaurus of “proxy”, and idk maybe choose: Deputy (in the meaning of: “A person/thing appointed or empowered to act for another”).