Everything is a trade off. The other extreme is having many libraries with overlapping concerns where the same security holes show up again and again. I think

Everything is a trade off. The other extreme is having many libraries with overlapping concerns where the same security holes show up again and again. I think the real answer is to decide on a strategy and then put healthy process in place to mitigate the downsides. In the case of sharing code across the company, make sure there are 2+ maintainers. This sort of succession planning is common. It is not foolproof, but it does mitigate the issue you raised.