fwiw as a former npm registry engineer i can tell u that "hundreds of download every month" likely is a result of the background bot activity npm gets. but your advice is sound! definitely vet your deps before you use them! and YES! read the source.
Re:Hello wasm-pack
by probablycorey on Wednesday April 18, 2018 @02:23PM
(#16869666)
Is this realistic though? Every time you update a dependency you would have to read its source (and its source dependencies, and their source dependencies...)
To do that well, it would be someone's fulltime job to read and do security audits on all those dependencies.
Last time I went to one of the Bay Area node meetups, that given meetup was being sponsored by just such a company. Can't remember the name, unfortunately.
The idea was though that you'd feed them your package.json and they'd let you know of any vulnerabilities, iirc. Or maybe they had a private repo of packages they'd checked? Can't remember.
Re:Hello wasm-pack
by tomsmeding on Wednesday April 18, 2018 @03:08PM
(#16870082)
Possibly https://snyk.io/ ?
Re:Hello wasm-pack
by illustrioussuit on Wednesday April 18, 2018 @02:46PM
(#16869878)
Theoretically, once something is updated all you would have to do is check the diff. Still tedious though.
I look forward to all the clever exploits that result from benign-looking code being added to benign-looking code.
Re:Hello wasm-pack
by mpolichette on Wednesday April 18, 2018 @02:25PM
(#16869697)
The argument in that article is that it doesn't matter what is in the source. The published package has no guarantees to be from the source.
For anything serious, read the source code, at the very least check your dependencies.