3 ms·
I think it is. It's way too normal to build a product and pull source code from hundreds or even thousands of packages that you have no idea about. Even worse,
by jeroenhd 4y ago
I think it is. It's way too normal to build a product and pull source code from hundreds or even thousands of packages that you have no idea about. Even worse, loading these dependencies may execute install scripts that have full access to your dev computer.
Open source is fine and using it is great. I trust many dev teams, but not all. Many languages (JS, Python, Rust, Go) have a super extensible, developer-friendly library of open source components for you to reuse, but this model also encourages relying on these tiny libraries often written by volunteers with no time to prune and maintain their own dependency tree.
Personally, I try to just grab the code I need from small projects (with a link back to the library of origin) rather than add the dependency. This makes license management more difficult (as the source code usually comes with license terms) but packages like left-pad are better off in some kind of helper folder than in the dependency graph.