EMENDANT

APIs change.
Your code adapts.

Emendant automatically detects breaking API changes, updates the code they affect, and verifies the migration.

Get started View on GitHub
PRODUCT PREVIEW
emendant / scan local
$ npx emendant scan
openai4.104.0 5.0.0
3 API changes affect this repository
× src/lib/uploads.ts:14
Removed fileFromPath helper
14file: await fileFromPath(path)
^
14file: fs.createReadStream(path)
✓ amendment verified
3 changes2 filesmigration ready →

THE PROBLEM

API upgrades shouldn't mean code archaeology.

Migration guides tell you what changed. They don't tell you where your code is affected, or whether the fix actually works.

Without EmendantMANUAL
  1. 01

    Read the changelog

  2. 02

    Decode the migration guide

  3. 03

    Search every workspace

  4. 04

    Find affected call sites

  5. 05

    Work out each replacement

  6. 06

    Make the changes

  7. 07

    Run tests

  8. 08

    Hope nothing broke

With EmendantAUTOMATED
  1. 01

    Read the API change

  2. 02

    Find affected code

  3. 03

    Apply the amendment

  4. 04

    Verify the migration

Migration ready.
Every affected call site accounted for.

THE AMENDMENT

See exactly what changed.

One breaking change. Every affected call site. A migration you can inspect.

src/lib/uploads.tsOpenAI SDK v5 migration
BEFOREopenai@4.104.0
01 import { fileFromPath }
02   from "openai/uploads";
03
14 file: await fileFromPath(path)
^AMEND
AFTERopenai@5.0.0
01 import fs
02   from "node:fs";
03
14 file: fs.createReadStream(path)
✓ Breaking change detected✓ Call site amended✓ Typecheck passed✓ Tests passed

Emendant detected the breaking change, updated the affected call site, and verified the migration.

BETTER TOGETHER

Dependabot updates the package.
Emendant handles what comes next.

Keep the dependency automation you already trust. Emendant picks up the handoff when a new version changes the API your code calls.

01DEPENDABOT

VERSION UPDATE

Package updated

openai 4.104.0 → 5.0.0
02⌃ EMENDANT

API ANALYSIS

Breaking changes found

3 changes · 2 affected files
03⌃ EMENDANT

CODE AMENDMENT

Call sites updated

precise, reviewable changes
04VERIFIED

VALIDATION

Migration ready

✓ typecheck   ✓ tests

HOW IT WORKS

From breaking change to working code.

A precise four-stage system. Each step produces evidence for the next.

01→

Detect

Know when an API changes.

Emendant tracks structured changes across the SDKs your code depends on.

02→

Analyse

Find where you're affected.

Import-aware matching maps each change to the exact call sites in your repository.

03→

Amend

Fix the migration precisely.

Deterministic transformations first. AI only when reasoning is genuinely required.

04→

Verify

Don't trust. Verify.

Typechecks and tests run before Emendant proposes the change for review.

THE CHANGE FEED

Built for the APIs developers depend on.

Emendant starts with fast-moving AI SDKs, backed by a curated, source-linked record of every change.

OOpenAIAVAILABLE FIRST
AAnthropicPLANNED
▲Vercel AI SDKPLANNED
LLangChainPLANNED

TRUST BY DESIGN

Your code stays yours.

Built around a simple rule: source code belongs on your machine.

Local-first

Scan repositories without uploading source code.

Read-only by default

No surprise writes. You stay in control of every change.

No source retention

Your source is never stored by Emendant.

Verified changes

Migrations are tested before they are proposed.

Local by default.Only the change feed leaves the network. Your repository doesn't.

READY WHEN YOUR API ISN'T

Stop chasing
API changes.

Let Emendant handle the migration.

View on GitHub