Detect Contract Break
Detect breaking changes across upstream package versions and lockfile entries.
Requests, breaking changes, and deterministic patches in one calm workspace. Free for teams up to 10.
The source parameter has been renamed to payment_method in mockpay v2.0.
source→payment_methodTRACKED ECOSYSTEM CONTRACTS & UPSTREAM REGISTRIES
Automated breaking change discovery, AST call-site mapping, deterministic patch synthesis, and human-gated GitHub delivery.
Detect breaking changes across upstream package versions and lockfile entries.
Map call sites with AST analysis to identify affected code paths.
Review minimal deterministic diffs alongside verified test output.
Upstream release bump from version 1.2.4 to 2.0.0 deprecates source. Contract prober identified required replacement: payment_method.
{
"changeId": "mockpay-2.0.0",
"package": "mockpay",
"versionRange": "1.2.4 -> 2.0.0",
"classification": "Parameter Rename",
"deprecatedSymbol": "source",
"replacementSymbol": "payment_method",
"scope": "call_site_parameter"
}The workspace keeps the changed API contract, affected call sites, and proposed diff close together with single-use approval verification.
source renamed to payment_methodsource: source,payment_method: source,Each step is visible: baseline green, bump red, deterministic fix, and green re-test.
A recorded change record explains what changed between two package versions.
Static analysis maps matching call sites in the repository.
A deterministic AST patch generates the smallest relevant rename.
The test suite runs in an isolated proof loop and reports before and after results.
The interface follows a strict detect, map, patch and prove sequence with human approval before PR delivery.
The prototype demonstrates a known breaking change using a bundled API fixture. Live provider watching is in development.
Parameter renamed: source becomes payment_method in charge creation payload.
Core capabilities combine AST static analysis, lockfile dependency mapping, and tamper-evident proof bundles. Untrusted customer code execution remains strictly fail-closed until qualified microVM sandboxes are active.
The engine explains recorded parameter renames in plain language with verified breaking change classification.
Static AST analysis maps matching call expressions across source code and lockfile dependencies.
The proof loop generates a minimal diff and captures baseline, red, and green test execution output.
Select a plan below to checkout directly via PayPal. Payouts route straight to your account with instant activation.
For individual developers testing deterministic AST migrations on local fixtures.
Automated package watching, call-site mapping, and verified migration proof runs.
Unlimited repositories with team governance, RBAC, and custom migration rules.
Dedicated microVM sandboxing runners, private npm registries, and custom SLAs.
Honest overview of implemented capabilities, security boundaries, and planned milestones.
Yes. The free plan is completely free for teams up to 10 members with full AST call-site analysis, deterministic patch generation, and local proof verifications.
Package registries and breaking change records are tracked via configured watch targets. Live continuous provider polling is active for admitted packages.
Yes. Authenticated users and workspaces are persisted in PostgreSQL. The dashboard displays connected repositories, package watch targets, and migration findings with tenant isolation.
Yes. Pull request delivery uses GitHub App installations with strict single-use human approvals, diff-hash enforcement, and delivery mutex locking.
No. Arbitrary customer code execution is fail-closed blocked on application hosts. Full red-to-green test execution is restricted to vetted repositories until containerized microVM isolation is provisioned.
Requests, breaking changes, and deterministic patches in one calm workspace. Free for teams up to 10.
Start for free