driftlineLAB 01Runs on your device

THE SPACE BETWEEN TWO API VERSIONS

Change happens.
Catch the drift.

Turn an API update into a migration plan.
See what breaks, where to look, and what to change.

Explore the demo ↘Open source. No signup. No uploads.

YOUR MIGRATION WORKSPACE

Two contracts. A clear next step.

before.json
BEFORE or drop a JSON file here
after.json
AFTER or drop a JSON file here

OpenAPI 3.0 / 3.1 · JSON · up to 5 MiB each

Optional · locate candidate callers

Loading the example…

SMALL TOOL. USEFUL SIGNAL.

From changelog
to change list.

01

Compare the contract

Request and response changes are checked in opposite directions. Ambiguous changes go to review.

02

Find the starting point

Add client source files to find literal endpoint and SDK name references, with file and line numbers.

03

Take it into CI

Export Markdown or JSON. Run the same engine from the CLI and fail a build on breaking changes.

SAME ENGINE, YOUR PIPELINE

Keep the next surprise out of main.

node bin/driftline.mjs old.json new.json \
  --source ./src --fail-on review
Get the CLI ↗

A migration assistant, not a compatibility proof. Complex schemas and unresolved refs require review. Source references are text matches, not verified usages. Run your consumer tests before shipping. Read coverage & limits ↗