It doesn't have to be actually invented, you can just build everything yourself.
Point is take that mindset ("Never assume anyone else in this organization knows anything"), quickly becomes never trust anyone else, and degenerates to - we'll need to rewrite the gluons (luckily people give up after they spend all their free time).
I prefer the Chesterton's fence. If you don't know what it does you can't remove it.
> I find it is generally a mistake to just bring in dependencies
I don't agree.
It's a pick your poison situation. Use dependency and have a centralized source of mistakes or distribute mistakes, e.g. billions of xml parsers suffering the same issue.
In my experience cautious use of dependencies is preferred, but I would take a well known devil. Over a homebrewed one.