This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
Drift — Dependency Upgrades
Find and fix breaking dependency changes
Drift checks dependency updates against your actual repository. It computes API differences from published package artifacts where possible, maps changed APIs to exact files and call sites, keeps uncertainty explicit, and prepares reviewable fixes. MIT-licensed open source, available in VS Code, the CLI, GitHub Actions, and through MCP.
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?
About Drift — Dependency Upgrades on Product Hunt
“Find and fix breaking dependency changes”
Drift — Dependency Upgrades was submitted on Product Hunt and earned 0 upvotes and 1 comments, placing #158 on the daily leaderboard. Drift checks dependency updates against your actual repository. It computes API differences from published package artifacts where possible, maps changed APIs to exact files and call sites, keeps uncertainty explicit, and prepares reviewable fixes. MIT-licensed open source, available in VS Code, the CLI, GitHub Actions, and through MCP.
On the analytics side, Drift — Dependency Upgrades competes within Open Source, Software Engineering, Developer Tools and GitHub — topics that collectively have 673.8k followers on Product Hunt. The dashboard above tracks how Drift — Dependency Upgrades performed against the three products that launched closest to it on the same day.
Who hunted Drift — Dependency Upgrades?
Drift — Dependency Upgrades was hunted by Rodolphe Kouyoumdjian. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of Drift — Dependency Upgrades including community comment highlights and product details, visit the product overview.
Rodolphe Kouyoumdjian