This is off-topic, but at the top of the readme is this:
> The name is somewhat of a poor choice, but it was available on npm.
npm has supported scoped packages [0] for years now, and it's a fantastic solution to this problem, as well as solving many others (like typosquatting in many cases).
I know this package is already named, but I really urge people to use scoped packages more.
Why not making scopes mandatory, to fix these issues once and for all? Wait, that's what GitHub did for 10 years ...
Would it though? I've noticed a trend of libs being created under orgs of the same name, e.g.
- https://github.com/angular/angular
- https://github.com/rollup/rollup
- https://github.com/cherow/cherow
- https://github.com/hyperapp/hyperapp
Wouldn't we end up with a similar situation?