I think it's something I really want to have. The name conflict I think should be finally a serious problem. Once instance for this is:
jemalloc is a low quality wrapper for jemalloc, undocumented and not maintained.
And the first time I want to use jemalloc allocator, I just add that crate and not working. But the correct crate should be import is
jemallocator which isn't a good name for it in my opinion.
In long term, I believe this would finally become a problem if there's nothing to prevent people occupying meaningful name meaninglessly.
There are a lot of well-known term which is squatted by meaningless crate already, I don't think the long term solution should be leave them there forever.
I do really think it's better to make all crate have
user::crate namespace and some community adopted crate can have a top-level alias. And the top-level alias is maintained and reviewed by the crates.io team. (And I believe this is what Docker Hub is doing)
Another benefit would be people can have their own fork of some existing crate published under their own name. But currently it's very hard to have that.
But the problem is this will fundamentally break to most of existing code and introducing extra maintenance burden.
What I am saying is not suggesting any change, but I think there would be some issue in the future if the community keep growth.