# Repairo

> Repairo — Dependabot for third-party APIs. When a vendor API breaks your build, Repairo diffs the OpenAPI spec, finds affected call sites, and opens a PR with patches that typecheck.

Canonical site: https://repairo-steel.vercel.app/
LLM summary (full): https://repairo-steel.vercel.app/llms-full.txt
Machine-readable index: https://repairo-steel.vercel.app/llms.txt

## What Repairo does

Repairo is automated API maintenance for engineering teams:

1. Diff upstream OpenAPI 3.0/3.1 (or pinned snapshots) and classify breaking vs safe changes.
2. Map each breaking change to call sites — ts-morph for TypeScript/JavaScript; tokenizer paths for Python and Go.
3. Apply deterministic AST/token transforms (not free-form LLM rewrites). Optional `--agent-resolve` only for ambiguous enums.
4. Validate before proposing: TypeScript/JavaScript typecheck; Python/Go syntax (optional Pyright when configured).
5. Deliver a unified diff or GitHub pull request for human review — never auto-merge agent-assisted fixes.

Primary keywords: OpenAPI diff, API drift detection, breaking API changes, AST codemod, Dependabot for APIs, SDK migration, GitHub PR automation.

## CLI (offline, no signup)

    npx repairo-cli scan ./src --vendors stripe,openai,supabase
    npx repairo-cli init --repo owner/your-app
    npx repairo-cli check --vendors stripe,openai --target ./src
    npx repairo-cli diff --spec ./specs/new-openapi.json
    npx repairo-cli repair --dry-run
    npx repairo-cli repair --apply
    npx repairo-cli repair --create-pr

Requires Node.js 22+. Package: https://www.npmjs.com/package/repairo-cli

## Supported vendors

- OpenAI API: Automated AST repairs for OpenAI SDK migrations, model deprecations (e.g. gpt-3.5-turbo -> gpt-4o-mini), and Assistants API updates. — https://repairo-steel.vercel.app/agents/openai
- Google Gemini: Auto-patch Gemini AI model name updates, parameter shifts, and Google Generative AI SDK breaking changes. — https://repairo-steel.vercel.app/agents/gemini
- Anthropic Claude: Monitor and auto-repair Messages API parameter changes and Anthropic SDK breaking updates. — https://repairo-steel.vercel.app/agents/anthropic
- Stripe: Payments API. Watch public OpenAPI; repair TypeScript and Python consumers when the contract or version moves. — https://repairo-steel.vercel.app/agents/stripe
- Supabase: Track the Supabase Management API contract and repair TypeScript and Python consumers when endpoints or fields change. — https://repairo-steel.vercel.app/agents/supabase
- GitHub REST: GitHub REST OpenAPI from the official openapi repo — useful for tooling that calls api.github.com. — https://repairo-steel.vercel.app/agents/github
- Petstore (demo): Public Swagger Petstore OpenAPI — safe sandbox for install-agent demos without a real vendor pin. — https://repairo-steel.vercel.app/agents/petstore

## Pricing

- Free ($0): 1 integration(s), 15 repair runs/month, 3 seat(s). 1 watched integration; 15 repair runs / month; Open real GitHub PRs; Fixture demo playground.
- Pro ($29/month): 50 integration(s), 500 repair runs/month, 15 seat(s). 50 watched integrations; 500 repair runs / month; Team seats (15); Priority webhook processing; Billing portal & invoices.
- Enterprise (custom): VPC runner, SSO, private specs — https://repairo-steel.vercel.app/contact

## Key pages

- Documentation: https://repairo-steel.vercel.app/docs — CLI quickstart, command reference, GitHub App, security.
- Engine architecture: https://repairo-steel.vercel.app/docs/architecture — runRepair graph, CLI vs hosted validation.
- Self-host on Vercel: https://repairo-steel.vercel.app/docs/deploy — Neon, OAuth, env vars, Stripe, smoke tests.
- Pricing: https://repairo-steel.vercel.app/pricing — Free, Pro, and Enterprise plans.
- Vendor agents: https://repairo-steel.vercel.app/agents — Stripe, OpenAI, Anthropic, Supabase, Gemini, GitHub REST.
- Use cases: https://repairo-steel.vercel.app/use-cases — When teams use Repairo for API drift.
- Live demo: https://repairo-steel.vercel.app/demo — Browser OpenAPI diff → impact → patch without install.
- Blog: https://repairo-steel.vercel.app/blog — Engineering posts on AST repairs.
- Changelog: https://repairo-steel.vercel.app/changelog — Product and CLI release notes.
- Security: https://repairo-steel.vercel.app/security — OAuth scopes, data handling, compliance roadmap.
- About: https://repairo-steel.vercel.app/about — Company and mission.
- Contact: https://repairo-steel.vercel.app/contact — Sales, security questionnaires, support.
- Privacy: https://repairo-steel.vercel.app/privacy — Privacy policy.
- Terms: https://repairo-steel.vercel.app/terms — Terms of service.

## Blog

- How we built a deterministic AST engine to fix breaking changes (2026-08-12): https://repairo-steel.vercel.app/blog/how-we-built-the-ast-engine — Why regex can't safely migrate SDK calls, and how Repairo uses the TypeScript compiler API and ts-morph to generate compiler-validated AST repairs for breaking API changes.

## Frequently asked

- What happens to our code? For a repair job we fetch the OpenAPI spec and consumer files you point us at, process them in memory, and use that output to build a diff. We do not sell your code or use it to train third-party models. Workspace metadata (integration config, run status, PR links) is stored in our database; file contents are not kept as a long-term archive after the job finishes. See https://repairo-steel.vercel.app/security for OAuth scopes and retention details.
- What does Repairo fix? Breaking and risky changes in third-party OpenAPI specs — renames, removed fields, URL moves, enum changes, and similar contract drift. Repairo diffs the spec, finds affected TypeScript, JavaScript, Python, and Go call sites where we have transforms, runs compiler or syntax checks when configured, and opens a GitHub pull request for your team to review. It is not a general-purpose code generator.
- Why would my team use this? Because API updates still land in your repo as surprise compile errors, flaky tests, or production incidents. Repairo shortens the loop from “the vendor changed something” to “here is the diff that updates our clients,” with evidence attached instead of a manual file-by-file hunt.
- What happens when an API changes? On hosted plans, Repairo can poll vendor OpenAPI pins or react to spec changes in your repo (GitHub App or webhooks, depending on setup). When a breaking change is detected, it maps impact, prepares patches, and opens a PR. Nothing merges automatically — you review and merge on your schedule.
- Does Repairo find security vulnerabilities too? No. Repairo focuses on API contract drift and client repairs, not CVE scanning or dependency advisories. Use your existing security tooling for vulns; use Repairo when the API shape changed and your integration code needs to catch up.
- How do I get started? Fastest path: try the in-browser demo at https://repairo-steel.vercel.app/demo, or install the CLI (npm i -g repairo-cli) against a local repo. For your own GitHub repo, install the GitHub App or sign in to the workspace, pick a repository, and tell Repairo where the OpenAPI spec and client files live. Vendor agents add remote spec watching once an integration is configured.
- What is Repairo? Repairo — Dependabot for third-party APIs. When a vendor API breaks your build, Repairo diffs the OpenAPI spec, finds affected call sites, and opens a PR with patches that typecheck.
- Which languages are supported? TypeScript, JavaScript, Python, and Go share the same deterministic repair set (CLI + hosted).
- How is this different from Dependabot or Renovate? Those bump package versions. Repairo rewrites application call sites to match vendor OpenAPI contract changes and validates before proposing a PR.
- How is this different from Copilot, Cursor, or Devin? Repairo applies rule-based transforms from the OpenAPI diff; patches that fail tsc, Python syntax, or Go syntax checks are blocked.
- npm package: https://www.npmjs.com/package/repairo-cli (Apache-2.0, version 0.4.0)
- Source code: https://github.com/adityacs50-lab/Repairo