Reference
Data models & lifecycle
Field and enum names below match the actual database schema — this is documentation of what exists, not an aspirational API design.
Repository model
Each connected repository tracks its GitHub identity, default branch, whether it's private, a health score, and when it was last scanned.
API change model
A detected upstream change records its provider, a deduplication fingerprint, change type, severity, whether it's breaking, the affected resource/operation/field, effective and deprecation dates, its source and confidence, and its own lifecycle status:
| DETECTED | Persisted, not yet analyzed against any repository. |
| CONFIRMED | At least one repository was confirmed affected. |
| ANALYZED | Impact analysis has completed for this change. |
| ACTION_REQUIRED | At least one impact scored High or Critical risk. |
| MIGRATION_IN_PROGRESS | A migration attempt has been queued. |
| RESOLVED | A linked migration reached Draft PR opened. |
| IGNORED | Manually dismissed by a human — never set automatically. |
Finding model
A finding is a specific, actionable call site: the file, line, symbol, the detected and target SDK versions, a description of the breaking change, and a status — open, patched_by_shim (legacy), pr_opened, or resolved.
Migration lifecycle
| QUEUED | Accepted into the migration worker's queue. |
| SCANNING | Cloning and re-scanning the repository. |
| GENERATING | Generating the migration patch. |
| VALIDATING | Running deterministic AST, safety, and re-scan gates; repository commands run only in an explicitly enabled isolated sandbox. |
| BLOCKED | Validation failed, or a safety constraint stopped it. |
| PR_CREATED | A Draft pull request is open, awaiting review. |
| FAILED | An unrecoverable error occurred. |
Provider support
See the provider matrix on the homepage for current support status by provider and category.
Stripe is the only live provider adapter. Automated compatibility findings currently cover 15 symbols: charges.create, charges.capture, customers.createSource, customers.update, orders.create, paymentIntents.create, paymentIntents.confirm, invoices.pay, subscriptions.create, subscriptions.update, checkout.sessions.create, webhooks.constructEvent, balance.retrieve, terminal.readers.processPaymentIntent, and refunds.create. Other Stripe calls can appear in the dependency map but are unclassified; absence of a finding does not prove complete Stripe compatibility.