Re:Alert: NPM modules hijacked
by prodigal_erik on Wednesday March 23, 2016 @05:29PM
(#11348408)
If any of thousands of strangers could push a button and prevent me from deploying to production, I have made several bad decisions. This seems to apply to the majority of NPM users.
[ Parent
| on HN ]
> If any of thousands of strangers could push a button and prevent me from deploying to production, I have made several bad decisions.
That's a strange thing to say considering how insanely complex modern hardware and software are. While the NPM setup is indefensible, there are countless ways a stranger can prevent your deployment, if that stranger works at Microsoft, Intel, or the manufacturer of any production hardware component. OS bugs, driver bugs, compiler bugs, and hardware/microprocessor bugs are a thing. At any point, you are dependent on the work of many thousands of strangers, no matter how perfect your decisions are.
Re:Alert: NPM modules hijacked
by prodigal_erik on Sunday March 27, 2016 @09:10PM
(#11372200)
A proper build is hermetic. Sure we have to deal with pre-existing bugs, but nobody outside our org can make intentional changes to our build today without our actively consenting to deploy their updates after first testing them.