> Enforce scope (namespace) requirement, and require external verification (reverse DNS for example).
Who the heck says everyone who publishes a library has a domain? That seems absurd.
Who the heck says everyone who publishes a library has a domain? That seems absurd.
This exists because domains (historically) used to be expensive by western standards. .com used to be $75/year back in the day.
Don't count other people money.
A small bar of $20/year is also enough to completely cut-down on contributors who sign up with the intention of publishing malicious packages: they have to pay $20/year for each malicious package they want to publish!
Heck domain names are ephemeral, forget a deadline by a day and they are snatched up my squatters. They don't provide any extra guarantees. Do we really think a domain requirement is going to stop state level actors that are already stealing 2FA package publishing tokens from major software orgs?
Is that your target? Because if so, then nothing will stop them.
Requiring domain name verification is not going to do anything when 2FA tokens are being stolen.
What it will do is prevent students and people who want to stay anonymous from contributing to open source.