Sure, but combined with other methods, you get something much better. Maybe I invent a protocol today called "hitta" and make a new package called "hitta" I'

Sure, but combined with other methods, you get something much better. Maybe I invent a protocol today called "hitta" and make a new package called "hitta" I'm pretty much automatically going to be the de facto standard, even if better, more updated implementations exist. Names matter. But if my implementation is called hittaorg/hitta Organizations and users (publishers) can be verified, and the tools integrate correctly; you gain better package context, increase trust, and reduce supply chain risks. Now, if user123 has a better version, they might make user123/hitta Instead of pyhitta-with-new-features or whatever garbage is used today