Another guideline: Avoid dependencies that have many dependencies of their own.
Another guideline: Avoid dependencies that have many dependencies of their own.
While I agree with you, good luck with that if you are using node/npm.
Good luck with nodejs apps :-)
"Carefully considered EACH dependency recursively" is not actionable advice (and nothing worst then tautology).
I rely on automatic tests and penetration tests.
The actionable advice is more like: Carefully consider if you need dependency. When you choose to use them, don't spend more then a dozen of minutes analyzing them internally but rely on automatic tests.
You mention penetration tests here (?), are those really less time consuming and more effective than taking 30 minutes to review a library?
Also you can outsource the tests and its easy to do. Depending on the contract, they can even be held liable if you come to get owned via the method that should have been tested.