3 ms·
This works until you consider regular security vulnerability patching (which we have compliance/contractual obligations for).
by SkyPuncher 11mo ago
This works until you consider regular security vulnerability patching (which we have compliance/contractual obligations for).
- Nextgrid 11mo agoThis only makes sense for vulnerabilities that can actually be exploited in your particular use-case and configuration of the library. A lot of vulns might be just noise and not exploitable so no need to patch.
- SkyPuncher 11mo agoYes and no. Problem is code bases are continuously evolving. A safe decision now, might not be a safe decision in the future. It's very easy to accidentally introduce a new code path that does make you vulnerable.