5 ms·
If you've ever run an `npm install` you've executed 100s of opaque binaries on your machine.
by bhedgeoser 4y ago
If you've ever run an `npm install` you've executed 100s of opaque binaries on your machine.
- paskozdilar 4y agoWould 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.
- Something1234 4y agoDo you really think your average javascript developer is going to read and understand all of their dependencies?
- leppr 4y agoThere is no open-source requirement, like there would be on Gentoo packages for instance. NPM packages frequently pull arbitrary binaries in their install scripts.
- bhedgeoser 4y ago1. 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.