3 ms·
I still think that sandboxing dependencies is the wrong answer to this problem. (first - the problem is trusting dependencies. How to spot malicious code in a
by marcus_holmes 6y ago
I still think that sandboxing dependencies is the wrong answer to this problem.
(first - the problem is trusting dependencies. How to spot malicious code in a dependency, and stop an evil upstream maintainer from doing bad things to your site)
This solution slows down the system at run-time (and also never quite solves the problem - sandboxes are pretty leaky. The history of browser extensions trying to do the same thing is a good example).
I'm not really sure what the solution is. I have some ideas, but they're mostly about changing the culture around coding, rather than technical.
- lolc 6y agoHaving sandbox restrictions available allows deeper defence. When it comes to running other people's code, VM restrictions provide a solid layer of protection. At work we're transitioning our NPM scripts to run in containers. This is very cumbersome. But the extra layer protects dev homedirs from rando NPM authors.