Earlier quoted context omitted.
This is a credentials and access list oAuth style problem, and not really intractable. For package X , I should be able to present my npm (homebrew, apt, nuget, etc) credentials with publishing rights for the package. If package X is of sufficient public interest (user count, nature/sensitivity of user data, downstream distribution, etc), then the public interest + cryptographic credentials should permit access to be…
This is not tractable, because there is nothing stopping me from copy-pasting someone else's project into my own namespace. Under most OSS licenses I have express permission to do so. If you try to do some kind of dupe-detection, someone can use a lightweight LLM to make superficial changes until it's considered a different project. Finally, the meatspace status quo is that it is totally acceptable to pay someone to…
Even if you don't, a lot of source code can be legitimately copied thanks to the GPL/MIT/BSD/etc. I'm allowed to take all of zlib and integrate it into my own project if I so chose.