> Moreover, you do manage to know _better_ the ins and outs of each bit of your system (because you wrote it, and the whole surface has been walked on at least

> Moreover, you do manage to know _better_ the ins and outs of each bit of your system (because you wrote it, and the whole surface has been walked on at least once). This only holds if you work only for yourself. > Unless you are of a specific interest to an attacker, not relying on external dependencies makes you less detectable as your app may not behave as scanner expect it to. Another argument can be made that you're investing too much valuable time into things that have been solved before - and likely better than a single person could manage. > But for any large project involving more than 4/5 people, perhaps relying on no external dependencies may be a bit complex to manage in the long run. In my experience, this is true for any one project with more than one (1) developer, even if the developer might change in the future. Any junior front end developer can be productive in a years old angular project. They might not be in a custom dependencyless project.