COMPARE
oasdiff Pro is an excellent rule-based breaking change gate. It posts reports to GitHub PRs with 450+ checks. StateAnchor is the next layer: LLM-evaluated verdicts, an auditable exception ledger, and compliance-grade reporting.
Honest context
StateAnchor uses oasdiff as a dependency for its diff engine. oasdiff Pro is a direct architectural competitor that launched April 26, 2026. This page compares them honestly. Both solve real problems. The question is which layer you need.
WHY NOT JUST USE OASDIFF?
oasdiff is rule-based (450 rules). StateAnchor adds LLM semantic evaluation for breaking changes that structural rules miss -- behavioral intent, implicit contracts, and context-dependent compatibility.
oasdiff has no exception governance. StateAnchor has a two-signal exception model: CODEOWNERS identity check plus 14-day production telemetry validation before an exception influences future gate behavior.
oasdiff produces no audit provenance. StateAnchor produces SOC 2-mapped compliance exports and writes every verdict to a public Merkle log.
They're compatible. StateAnchor uses oasdiff internally as one detection layer. oasdiff tells you what changed. StateAnchor tells you whether it's safe to ship.
CAPABILITIES
THE CORE DISTINCTION
oasdiff Pro’s 450+ rules are a comprehensive library for catching known breaking change patterns. They’re fast, deterministic, and excellent at what they do.
Rules have a structural limit: they match patterns, they don’t evaluate intent. A field renamed from amount to amount_usdis structurally a rename (WARN), but may be semantically a breaking change if downstream systems assumed the unit was already USD. StateAnchor’s LLM evaluation reads the endpoint context and evaluates whether the change is actually safe to ship to your consumers.
The second gap is exception governance. oasdiff Pro’s one-click approve is fast, but it’s a single actor bypassing the gate unilaterally. StateAnchor’s anergic two-signal model requires a second independent signal before a bypass activates -- the kind of dual-control that SOC 2 auditors look for.
Benchmark: 34-scenario ground-truth corpus
In our 34-scenario ground-truth corpus, structural diff tools catch 65% of breaking changes. StateAnchor catches 100%.
The gap comes from semantic context that rules cannot encode: auth scheme transitions (null→bearer is breaking for every unauthenticated caller), response type changes (integer→string on a response field breaks consumers reading it), and constraint tightening that is structurally additive but behaviorally breaking. See the full scenario breakdown at /docs/compare.
ALREADY USING OASDIFF PRO?
oasdiff Pro answers: “What rules did this change break?” StateAnchor answers: “Is this change safe to ship to all consumers?” These are different questions. A change can pass 450 rules and still break consumer behavior.
StateAnchor uses oasdiff internally as one of its detection layers -- it is not a replacement. If you are already running oasdiff Pro for diff visibility, StateAnchor adds the gate decision layer on top: LLM-evaluated verdict, categorical ERR/WARN/INFO lane, SOC 2 compliance export, and the anergic exception ledger.
FEATURE COMPARISON
| Feature | oasdiff Pro | StateAnchor |
|---|---|---|
| Breaking change detection | Yes -- 450+ rule-based checks | Yes -- rules-based detection plus LLM-evaluated verdict |
| LLM-evaluated verdict | No -- rule matching only | Yes -- LLM evaluates semantic intent, catches what rules miss |
| GitHub PR integration | oasdiff Pro: posts report to PR with one-click approve/reject | GitHub Action with OIDC, auto PR annotation, ERR blocks merge |
| Exception governance | One-click approve on the PR report | Anergic two-signal ledger -- requires two independent signals, signed and auditable |
| SOC 2 compliance export | Not included | Machine-readable audit evidence per gate decision, exportable per run |
| Gate reliability reporting | Not included | Gain margin confidence bands on every verdict |
| Multi-baseline comparison | Two files -- point-in-time only | Four syndromes: parent, merge-base, last-known-good, deployed |
| Drift audit trail | Not included | Append-only tamper-evident audit log -- every gate decision permanently recorded |
| SDK / MCP generation | Not included | TypeScript, Python, Go SDKs + MCP server on passing gate |
| Setup required | Single binary or npm package; oasdiff Pro adds GitHub App | GitHub App installation + stateanchor.yaml |
DECISION GUIDE
StateAnchor’s free tier includes the gate engine. Connect a repo in ~=5 minutes.
Free to start. No credit card required.