New CVEs every day, migrations every sprint: I built an autopilot for both

Description and use

<p>Every week brings a new batch of CVEs. Every sprint, some framework, runtime or driver reaches end of life. And in any company older than a couple of years, the code does not live in one repository: a Java backend talks to an Angular front-end, both depend on a Python ops layer and an Oracle database, and each of them pins its own versions.</p> <p>Keeping that up to date by hand means someone, somewhere, tracking release notes, reading advisories, guessing which upgrade breaks which module, and in which order. It does not scale, and the gap between "a fix exists" and "the fix is in producti

Problem

<p>Every week brings a new batch of CVEs. Every sprint, some framework, runtime or driver reaches end of life. And in any company older than a couple of years, the code does not live in one repository: a Java backend talks to an Angular front-end, both depend on a Python ops layer and an Oracle database, and each of them pins its own versions.</p> <p>Keeping that up to date by hand means someone, somewhere, tracking release notes, reading advisories, guessing which upgrade breaks which module, and in which order. It does not scale, and the gap between "a fix exists" and "the fix is in producti

Outcome

<p>Every week brings a new batch of CVEs. Every sprint, some framework, runtime or driver reaches end of life. And in any company older than a couple of years, the code does not live in one repository: a Java backend talks to an Angular front-end, both depend on a Python ops layer and an Oracle database, and each of them pins its own versions.</p> <p>Keeping that up to date by hand means someone, somewhere, tracking release notes, reading advisories, guessing which upgrade breaks which module, and in which order. It does not scale, and the gap between "a fix exists" and "the fix is in producti

Evidence

New CVEs every day, migrations every sprint: I built an autopilot for both

Source