News for hackers. Stuff that matters.
Re:Npm operational incident, 6 Jan 2018 by vl-y on Sunday January 07, 2018 @05:22PM (#16093069)
Such explanation looks misleading to me. Even having the module detected as potentially malicious, why was it put into a state that such module doesn't exist, letting others publish package with the same name. For me it looks like there is something wrong at the npm side internally with the processes.

There are no comments on this comment yet.