Integrations
Only a granted change can proceed.
The two required contexts are CodeRifts / issuer and CodeRifts / contract-gate. The App alone does not block a merge until branch protection requires the check. On its own the check does not.
MCP (app.coderifts.com/mcp), host adapters (@coderifts/agent-hooks) and the keyless /api/v1/action-verdict are product surfaces too. They are not this CI catalog.
CodeRifts ships integrations for GitHub and Bitbucket Pipelines, and a GitLab CI recipe — plus a CLI that runs anywhere Node.js does, and a REST API for any other CI. Those are the ones we ship and document; a platform not in that list is reachable through the API, not through an integration we maintain.
Not every path prevents a merge or a tool call. Read what each path does (and does not) before treating a report as a gate.
GitHub App
The two required contexts are CodeRifts / issuer and CodeRifts / contract-gate. The App alone does not block a merge until branch protection requires the check.
GitHub Actions
The two required contexts are CodeRifts / issuer and CodeRifts / contract-gate. On its own the check does not.
GitLab CI
Recipe, not listed. A .gitlab-ci.yml posts /api/v1/diff. The catalog component is not published.
Bitbucket Pipelines
Add a CodeRifts contract check to your bitbucket-pipelines.yml for API governance on every Pull Request.
REST API
Call the API from any CI/CD system, script, or application. It returns an analysis — no grant, no receipt, and nothing it prevents on its own.
CLI
Run CodeRifts from your terminal. diff analyses locally with no key; the gates — deploy-gate, publish-gate, registry-gate — are the gating commands: they stop a deploy, publish or registry push in the pipeline that runs them — a pipeline gate, not a provider-enforced boundary. npx coderifts diff works anywhere Node.js runs.