Detect. Scan. Mend.

Cracks appear upstream. mendapi welds them shut.

Every fracture on this page is an upstream breaking change. Watch the gold seams close — that is the product: detect the break, find the blast radius in your code, preview the mend.

Tap to fracture · scroll to mend

The pipeline

01

Watch upstream

We monitor 20+ providers — Stripe, OpenAI, AWS, Shopify, Slack, Cloudflare and more — across SDK release feeds and official changelogs. Every entry is classified: breaking, deprecation, additive, fix. Pre-release channel noise is filtered out by default.

02

Scan locally

Run npx mendapi sync once to pull the change feed, then npx mendapi scan inside your repo. In under 30 seconds for repos up to ~2,000 files you get file-and-line impact: which breaking changes actually touch symbols your code uses. That budget is measured, not aspirational: a 2,000-file repo is about where 30 seconds runs out. Large monorepos take proportionally longer. Three evidence tiers keep the report honest — high means a changed symbol was found in your code, not just a mention of the provider.

03

Preview the mend

Run mendapi fix for a local diff built from official migration guides. Every patch is verified to apply cleanly with git apply and pass a syntax check before you ever see it. Review it, apply it, ship it.

Precision over noise

Evidence-gated

Alerts must earn the screen

A finding only reaches high confidence when a changed symbol is matched at an identifier boundary in your files. Provider brand names, env-var lookalikes and monorepo sub-packages you do not use are filtered, not shown.

Source-aware

SDK releases vs API changelogs

An SDK breaking change can only hit code that imports the SDK. An endpoint-level changelog entry can hit any raw HTTP client. mendapi applies different evidence rules per source, so both paths stay accurate.

Regression-locked

Gold fixtures guard every release

Known-answer fixture repos assert what must be flagged and what must stay silent. Every change to the scanner runs against them — precision cannot silently regress.

30 seconds to truth

$ npx mendapi sync
change feed synced — 84,112 changes across 20 providers

$ npx mendapi scan --out impact.json
mendapi v0.5 — scanning 1,039 files, network: off

stripe   breaking  high    lib/billing.js:14   setTimeout removed in v8
stripe   breaking  high    lib/billing.js:22   setApiVersion removed in v8
openai   deprecation medium src/embeddings.js:8 createEmbedding renamed

3 impacts across 2 providers. 27 changes checked, 24 filtered as noise.
$ npx mendapi fix --from-report impact.json
1 migration available: stripe-v7-to-v8 (official migration guide)
patch written to .mendapi/stripe-v7-to-v8.patch — review before applying