APIs change.
Your code adapts.

Updates to the software your product relies on can break important features. Emendant helps your team find the affected code, prepare a fix, and check the result.

See how it works Developer guide
emendant / scan local
$ npx emendant scan
openai4.104.0 5.0.0
1 change affects this project
× src/lib/chat.ts:14
OpenAI moved a chat feature
14client.beta.chat.completions.parse()
^
14client.chat.completions.parse()
✓ automatic fix available, checks shown after use
1 change1 filefix available →

Software updates can leave hidden work behind.

Release notes tell you what a provider changed. They rarely tell you which parts of your product need attention. Emendant helps your team make that connection.

Without Emendant
  1. 01

    Read the release notes

  2. 02

    Work out what changed

  3. 03

    Find the parts that use it

  4. 04

    Decide what needs updating

  5. 05

    Make the changes

  6. 06

    Check that they work

  7. 07

    Review anything you missed

With Emendant
  1. 01

    See the relevant changes

  2. 02

    Find the affected code

  3. 03

    Review a suggested fix

  4. 04

    See what checks passed

A clearer next step.
Your team can review what was found and checked.

See the problem and the proposed fix.

This example shows one change that Emendant can find and update without a model.

src/lib/chat.tsOpenAI software update
BEFOREopenai@4.104.0
14 client.beta.chat
15   .completions.parse()
^AMEND
AFTERopenai@5.0.0
14 client.chat
15   .completions.parse()
✓ Change found✓ Fix prepared automatically✓ Checked in a separate copy✓ Results shown to your team

Emendant can prepare this specific fix automatically. It then reports which checks passed in your project. Harder changes may need a developer or optional AI help.

After the update,
see what needs work.

If your team uses an automatic update tool, Emendant helps with the code changes it leaves behind. Dependabot is one example.

01DEPENDABOT

SOFTWARE UPDATE

New version installed

openai 4.104.0 → 5.0.0
02⌃ EMENDANT

FIND THE IMPACT

Affected code found

change and location shown
03⌃ EMENDANT

PREPARE A FIX

Suggested update ready

focused change to review
04CHECKED

CHECK THE RESULT

Results made clear

✓ available checks reported

Know what needs attention.

Emendant follows four steps to help your team handle supported software changes.

01→

Track

See what changed.

Emendant keeps a record of changes to the software tools your product uses.

02→

Find

See where it matters.

It checks your project and points to code that uses a changed feature.

03→

Update

Review a suggested change.

For supported changes, it prepares a focused fix. Some updates still need a developer's judgement.

04→

Check

Know what was checked.

It checks the fix in a separate copy and tells you whether your project's own checks passed.

Works with tools your team may already use.

Emendant covers selected changes from these providers in JavaScript and TypeScript projects. See the supported projects guide for current coverage.

OOpenAIopenai
AAnthropic@anthropic-ai/sdk
▲Vercel AI SDKai
LLangChainlangchain, @langchain/core
GGoogle Gen AI@google/genai
Request an API or SDK

Stay in control of your code.

You can scan a project on your computer before you decide whether to use a fix.

Scan on your computer

A scan checks your code locally.

Start without changes

A scan shows what it finds and does not edit your files.

Choose optional AI help

You decide if Emendant can ask an AI service for help with a harder fix.

See the checks

Each fix states what was checked and what passed.

Fixes and optional AI help can use the network. Learn when and what is shared in the privacy notice.

Spend less time
on broken updates.

See which supported changes affect your project, then decide what to fix.

Developer guide