Security Patching & Upgrades
Out-of-date frameworks, vulnerable packages and failing scans. We upgrade in safe steps with tests, so patching stops being a project.
Signs you are here
- A security scan or customer review flagged vulnerable packages
- The framework version is end-of-life
- Upgrades keep getting postponed because they break things
If production is down right now, call instead of using the form.
How we approach it
- Inventory Every dependency, version and known vulnerability.
- Plan Upgrade order that keeps the app working at each step.
- Upgrade Small, tested releases instead of one risky jump.
- Automate Dependency alerts and a routine so it does not pile up again.
End-of-life dates to plan around
After these dates the upstream project stops shipping security fixes. The application keeps running, but new vulnerabilities stay unpatched. We move apps to a supported version in small, tested releases.
| Runtime | End of security support | Supported target | Source |
|---|---|---|---|
| .NET 8 (LTS) | .NET 10 | Schedule | |
| .NET 9 (STS) | .NET 10 | Schedule | |
| PHP 8.1 | PHP 8.4 or later | Schedule | |
| PHP 8.2 | PHP 8.4 or later | Schedule | |
| Node.js 20 | Node.js 24 | Schedule | |
| Node.js 22 | Node.js 24 | Schedule |
Dates as published by each project, checked . Confirm on the project's page before planning.
Plan an upgradeQuestions
Will an upgrade break our app?
Every step is tested before release, and each release can be rolled back.
Stacks we support
- React
- Svelte
- Vue
- Node.js
- Python
- PHP / Laravel
- .NET
- WordPress
- iOS & Android
- AWS
- Google Cloud
- Azure