Hacker News new | ask | show | jobs
by bhedgeoser 1391 days ago
If you've ever run an `npm install` you've executed 100s of opaque binaries on your machine.
1 comments

Would you care to elaborate?

I always thought npm was open-source-centric. If npm somehow ran opaque binaries, I'd really like to know about that.

There is no open-source requirement, like there would be on Gentoo packages for instance. NPM packages frequently pull arbitrary binaries in their install scripts.
1. There are thousands of dependencies in a usual lockfile.

2. A package author can push something other than the repository contents to npm/ change contents before pushing to npm, making the whole open source thing useless.

3. As someone else pointed out, you can download+exec when an npm package is installed.

Do you really think your average javascript developer is going to read and understand all of their dependencies?