Provided by: npm_3.5.2-0ubuntu4_all
npm-disputes - Handling Module Name Disputes
1. Get the author email with npm owner ls <pkgname> 2. Email the author, CC firstname.lastname@example.org 3. After a few weeks, if there´s no resolution, we´ll sort it out. Don´t squat on package names. Publish code or move out of the way.
In almost every case so far, the parties involved have been able to reach an amicable resolution without any major intervention. Most people really do want to be reasonable, and are probably not even aware that they´re in your way. Module ecosystems are most vibrant and powerful when they are as self-directed as possible. If an admin one day deletes something you had worked on, then that is going to make most people quite upset, regardless of the justification. When humans solve their problems by talking to other humans with respect, everyone has the chance to end up feeling good about the interaction.
Some things are not allowed, and will be removed without discussion if they are brought to the attention of the npm registry admins, including but not limited to: 1. Malware (that is, a package designed to exploit or harm the machine on which it is installed). 2. Violations of copyright or licenses (for example, cloning an MIT-licensed program, and then removing or changing the copyright and license statement). 3. Illegal content. 4. "Squatting" on a package name that you plan to use, but aren´t actually using. Sorry, I don´t care how great the name is, or how perfect a fit it is for the thing that someday might happen. If someone wants to use it today, and you´re just taking up space with an empty tarball, you´re going to be evicted. 5. Putting empty packages in the registry. Packages must have SOME functionality. It can be silly, but it can´t be nothing. (See also: squatting.) 6. Doing weird things with the registry, like using it as your own personal application database or otherwise putting non-packagey things into it. If you see bad behavior like this, please report it right away.
· npm help 7 registry · npm help owner December 2015 NPM-DISPUTES(7)