You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The unrestrained automatic typosquat policy makes NPM unfriendly for developers which want to publish using a new, cool, short name.
I think an ability to do per-case risk-focused review (which would lead to allowlisting) would be useful and would solve this problem. Or adjusting automatic system to at least rank devs with lots of trust.
npmDiscussions around programming langages, open source and software developmentsource:uiDiscussions created via Community GitHub templates
1 participant
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Bug
Body
The unrestrained automatic typosquat policy makes NPM unfriendly for developers which want to publish using a new, cool, short name.
I think an ability to do per-case risk-focused review (which would lead to allowlisting) would be useful and would solve this problem. Or adjusting automatic system to at least rank devs with lots of trust.
All reactions