Re:Statement on NPM Package Vulnerability in v5.0.2-5.1.0 of...
by dboreham on Thursday November 29, 2018 @06:45PM
(#18565288)
I must be misunderstanding the attack: didn't it involve checking in malicious code to a repo used to build a package published in npm?
Or are you suggesting that all code in github should be considered untrusted, but somehow able to be verified by npm?
This hack has nothing to do with the scm but everything with the carelessness of npm.