Could npm adopt a reverse domain naming system similar to Java's for Maven libraries?

com.foo.bar

That would require domain verification, but it would add significant developer friction.

Also mandatory Dune reference:

"Bless the maker and his water"

I don't see how this solves the problem?

I was thinking something similar to cargo-audit, because domain names don't really fix anything here