Lately there was a compromised npm package, which was used as a dependency in various projects. The code allowed the attacker to steal funds if certain conditions were met.
Could Tezos become a victim of a similar attack with for example a hijacked OCaml dependency such as a commonly used library? How do the active developers working on the code try to prevent this? Don't quote me on this, but in an older video I can remember @ArthurB talk about code coverage - which is great. Are there other security measures in place? Or is it the job of the bakers to set up a sufficient firewall to prevent outside communication?