Readiness

Drift & Breaking-Change Radar

Spec vs implementation, spec vs contract, contract freshness and version-aware validation — one radar that catches drift before it reaches your consumers.

Drift score
74/100
Breaking gaps
2
Stale artefacts
0
Spec versions
1
4-way radar
Spec · Implementation · Contract · Version
Implementation70%Contract44%Test · Freshness100%Version70%
AlignedDriftingBrokenNo data
Per-API verdict
Drift health
74/100
Drifting

3 drift findings across 4 endpoints. Resolve breaking gaps first.

Investigate
Schema diff Change Intelligence Readiness scorecard
Per-endpoint
Drift matrix
AlignedDriftingBrokenNo data
EndpointImplementationContractFreshnessVersion
POST/orders
No dataAlignedAlignedNo data
GET/orders/{id}
No dataBrokenAlignedNo data
PATCH/orders/{id}
No dataDriftingAlignedNo data
POST/orders/{id}/fulfill
No dataBrokenAlignedNo data
Breaking changes
Impact list
2
  • highNo scenario covers GET /orders/{id}GET /orders/{id}CSV #2, #11

    This endpoint declares 2 responses but has no scenario validating any of them — the contract is unverified, so a breaking change here would pass CI undetected.

    Author at least a happy-path scenario for GET /orders/{id} (Scenarios → New) so its contract is exercised.
  • highNo scenario covers POST /orders/{id}/fulfillPOST /orders/{id}/fulfillCSV #2, #11

    This endpoint declares 3 responses but has no scenario validating any of them — the contract is unverified, so a breaking change here would pass CI undetected.

    Author at least a happy-path scenario for POST /orders/{id}/fulfill (Scenarios → New) so its contract is exercised.
  • lowSuccess response uncovered on PATCH /orders/{id}PATCH /orders/{id}CSV #2, #11

    Declared success response 200 has no scenario — coverage drift the green pipeline does not reveal.

    Add a scenario asserting 200 on PATCH /orders/{id}.
Contract freshness
Stale artefacts
fresh
No stale contract artefacts — scenarios and mappings are newer than the last spec change.