3 ms·
We're not particularly concerned about typosquatting for now. The name is based on the `.com`, i.e. all APIs / workflows built on Standard Library go to `userna
by keithwhor 7y ago
We're not particularly concerned about typosquatting for now. The name is based on the `.com`, i.e. all APIs / workflows built on Standard Library go to `username.api.stdlib.com`. The packages we use in NPM, RubyGems and Python are just called `lib`.
The way 99.99% of developers have used us to date is starting with our in-browser or CLI tooling which installs / requires the correct package automatically. So I think that removes some of the risk you're talking about. :)
You can hold on to the NPM package for now if you'd like! That's a good one. If we do find typosquatting becomes an issue, do you mind if I reach out?