api-drift

What it does

• Infers a schema from one or several sample responses, so a sometimes-absent field is recorded as optional rather than becoming tomorrow's false alarm.
• Classifies each change from the point of view of code that already consumes the old shape: removed field, changed type, became nullable and became optional are breaking; a new field is not.
• Stores the baseline as one JSON file with sorted keys, meant to be committed - so the change shows up in code review.
• Treats a non-2xx answer or a non-JSON body as an outage, not as drift.

How it is proved

Reproducible from two fixtures in the repository: it reports a rename as its two halves, a string that became a number, and a value that can now be null.

TypeScript25 testsruns in cron or CI

People find this looking for

detect API response schema change, API contract monitoring, breaking change detection JSON.

If that is your week and you would rather someone else did it, write to hello@dkautomation.dev or open an issue.