Laurie Voss

This action puts the wider interests of the community of npm users at odds with the wishes of one author; we picked the needs of the many.

Even within npm we're not unanimous that this was the right call, but I cannot see hundreds of builds failing every second and not fix it.

left-pad@0.0.3 is now restored to the registry. Run npm cache clear before attempting your installs again. This sucked and we're sorry.

This whole situation sucks. We will be carefully considering the issues raised by and publishing a post-mortem later.

In the meantime, several thousand open source projects have been repaired, and I'm sleeping fine tonight.

@seldo it wasn't your place to take another developers code and 'un-unpublish' it.

@seldo does that violate the license of the package?

@JonathanAbrams the code has an extremely liberal open-source license.

@seldo do we need to worry about malicious parties claiming the other freed up package names?

@JonathanAbrams All the freed names have been adopted by users who then identified themselves to us via email and verified their intentions.

@seldo are older versions (e.g. left-pad@0.0.3) going be re-published?

@seldo @npmjs Have you read the author blog post upon why it was unpublished?

@JakeDChampion @seldo @npmjs link?