Mitigation scenarios
Patch, isolate or replace?
Three responses to a compromise of express, scored on disruption, orphaning and effort. Baseline blast radius today: 6 packages, 6 applications.
Patch the vulnerability
Apply a security fix to the compromised package. It stays in the graph but its vulnerability is neutralized.
- Disruption
- Low
- Blast radius after
- 0 packages
- Orphaned packages
- 0
- Effort
- Low
Assumes a patch is available upstream and fully effective against the disclosed vector.
Isolate the package
Sever every connection to the compromised package. Dependents must find alternatives or lose functionality.
- Disruption
- High
- Blast radius after
- 0 packages
- Orphaned packages
- 0
- Effort
- High
Severs 6 dependency edges; 0 packages would be left with no remaining dependency and may lose functionality.
Replace with fastify
Swap the compromised package for a safe alternative and redirect every dependency edge to it.
- Disruption
- Medium
- Blast radius after
- 0 packages
- Orphaned packages
- 0
- Effort
- Medium
Requires an API-compatible alternative and regression testing across every dependent.
RippleLab recommendation
Recommended: REPLACE. For express (Ripple Score 1.00), swapping to fastify achieves full risk elimination with moderate effort and keeps all 6 dependents wired into the graph. Patching is viable only if the maintainer releases a verified fix inside your risk window — at this centrality, waiting is itself a risk. Isolation would orphan 0 packages and is not recommended unless containment is urgent.
Side-by-side metrics
| Metric | Patch | Isolate | Replace |
|---|---|---|---|
| Disruption | Low | High | Medium |
| Blast radius after | 0 | 0 | 0 |
| Orphaned packages | 0 | 0 | 0 |
| Implementation effort | Low | High | Medium |
| Reversible | Yes | Yes, with downtime | Yes |