apiweiser-cli watches your dependencies, confirms which updates actually break your code, and opens the pull request with the fix — before you ever run the upgrade.
curl -fsSL https://apiweiser-cli-fe.vercel.app/install.sh | sh Resolves how your code actually calls each dependency using TypeScript's type checker, not import-tracing — every link in a chained call is caught, even through wrapped or reassigned values.
Watches each dependency's GitHub releases, asks an LLM whether the latest one is breaking, and only acts once Renovate independently confirms the update is available — including security upgrades Renovate surfaces by checking releases against the OSV vulnerability database.
The coding agent runs on every proposed migration, but if the cached codemod already covers a repo's call sites, there's nothing to rewrite, so it doesn't spend extra tokens doing so. When a repo's call sites don't fit yet, it extends the existing codemod instead of starting over, so coverage only grows.
Bumps the dependency in package.json and the lockfile, applies the codemod for real, then branches, commits, and opens a PR against your repo — you just review and merge.
Once a release is classified as breaking, a coding agent builds and tests the migration, apiweiser bumps the dependency for real, and the PR lands on your repo — no further action needed from you beyond reviewing it.
The coding agent is invoked on every proposed migration — but if the cached codemod already covers a repo's call sites, there's nothing new to write, so it doesn't burn extra tokens rebuilding one. When it doesn't cover them yet, the agent extends the existing codemod instead of starting from scratch — so the registry gets more capable, not just bigger, with every repo it touches.