Hey Product Hunt! I built Drift because dependency updates kept leaving me with the same question: this package changed, but does it actually break my code? Most dependency tools tell you an update exists. Drift checks what that update does to your repository. It downloads both published versions, computes what actually changed in the API — from the artifacts, not the changelog — and maps those changes back to the files and call sites that use them. No curated migration recipes, so it works on the package nobody wrote one for. One thing I cared about a lot: uncertainty. Drift won't tell you an upgrade is safe. It tells you what it checked, what it found, and what it couldn't establish — and when you want certainty rather than analysis, one flag installs the upgrade in a scratch copy and runs your own build and tests. For fixes, Drift does what it can deterministically, then hands the upgrade to the coding agent you already use — in an isolated copy of your repo, never your working tree. It then checks every file that agent changed and reverts anything that cheats: a weakened test, relaxed compiler strictness, a quietly downgraded dependency. It never merges. Use it from VS Code, the CLI, GitHub Actions, or over MCP. MIT licensed, runs on your machine, no service. The accuracy benchmarks and the runs behind them are public, including the results that weren't flattering. I'd love feedback from people who deal with upgrades regularly: how do you decide whether an upgrade is safe to merge today?

Drift — Dependency Upgrades

Find and fix breaking dependency changes

Find and fix breaking dependency changes