Skip to main content
Free to Use — No Credit Card Required

Stop guessing which
upgrades will break.

You'll see what's vulnerable, what'll break if you touch it, and get a tested merge request to fix it.

200 Dependabot PRs. You close 190.
Updates pile up, get ignored, and only matter when something breaks.

app.verx.dev/projects/acme-app/scan
Before: raw npm audit
142 vulnerabilities (12 critical, 28 high, 47 moderate, 55 low)
nth-checkpostcssglob-parenttrim-newlinespath-parsenode-forgeminimatchjson5semverword-wraptough-cookiexml2js+130 more

run `npm audit fix` to fix 89 of them. Good luck with the other 53.

After: VerX intelligence
!
3 critical, fix nowaxios, jsonwebtoken, node-fetch
22 files
2 clusters readyreact ecosystem, eslint + prettier
grouped
139 safe, no action neededlow severity, unreachable, or transitive-only
filtered

Blast Radius: react 18 to 19

Impact mapped before you touch a single file

react 18.3.1 → 19.2.0
Major
Peer dependencies pulled inmust upgrade together
react-dom@types/react@types/react-dom
Files with breaking imports14 files
src/components/auth/login-form.tsxuseRef signature changed
src/hooks/use-fetch.tsforwardRef removed
src/app/layout.tsxReactDOM.render → createRoot
+ 11 more files
Downstream packages affected4 packages
nextreact-hook-form@radix-ui/react-dialogframer-motion

Sprint Impact

Manual maintenance vs VerX automation

Without VerX: manual process
Triage npm audit output2h
Research breaking changes3h
Test upgrade locally4h
Fix peer dep conflicts2h
Open PRs & wait for CI1h
Total per sprint~12h
With VerX: automated
Review prioritized report10m
Approve upgrade plan5m
Review merge request15m
Total per sprint~30m

CVE alerts before they hit production.

We check every package in your tree. You hear about it the moment something's wrong.

Node.js 20: End of LifeCRITICAL

Node.js 20 reaches end-of-life on April 30, 2026. No security patches after this date. Your CI runs on Node 20.18.1.

62 days remaining
Recommended: Node.js 24 LTS
@types/react v18: Upgrade RequiredWARNING

React 19 ships built-in TypeScript types. @types/react is deprecated for React 19+ projects. 3 packages depend on this.

Deprecated since React 19
Remove @types/react after upgrading
Next.js 16.2: Upgrade AvailableNEW VERSION

Next.js 16.2 is available with Turbopack stable, improved cache semantics, and 3 security patches. Codemod ready.

Released 2 days ago
1 breaking change · codemod available
react-router v5: DeprecatedCRITICAL

react-router v5 is no longer maintained. No security patches since March 2023. 14 files import from this package.

Unmaintained since 2023
Migration path: react-router v7
Upgrade Planner

Know what breaks before you touch it.
And which packages need to upgrade together.

React and react-dom can't upgrade separately. We know that. Packages that share peer deps get grouped and ranked by risk, so you tackle the right things first.

app.verx.dev/projects/acme-app/upgrade-plan

Review Plan

4 phases to complete

Phase 1: Patch Security FixesDone
12 packagesMerged
2
Phase 2: Tooling UpdatesNext StepAuto-Merge

ESLint, Prettier, and Vitest. No breaking changes expected.

18 packages8 auto-merge
3
Phase 3: Framework MinorCodemod

Tailwind CSS v4.1 + Prisma 6.5. Config migration required.

8 packages2 breaking
4
Phase 4: React 19 + Next.js 16

Cluster: react + react-dom + @types/react upgrade together

5 packages4 breaking1 project impact
Pre-Merge Checks
Pre-Merge Checks

Merge requests that arrive tested.
Each upgrade runs in isolation. Nothing ships until it passes.

Each upgrade runs in a sandbox. Breaking changes get fixed. Tests pass. And then you get a merge request to review.

Frequently Asked Questions

Dependency upgrades, handled.
You review. You merge. That's it.

Connect GitHub. First scan in 60 seconds.

No credit card required.