If you've ever run an `npm install` you've executed 100s of opaque binaries on your machine.
I always thought npm was open-source-centric. If npm somehow ran opaque binaries, I'd really like to know about that.
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.