CodeRifts vs Zally

CodeRifts provides authorization and governance for contract changes made by AI agents and API teams. Its diff engine checks OpenAPI 3.0 and 3.1 specifications for endpoint removals, newly required fields, response-type changes, enum restrictions, authentication changes, and parameter edits. It discovers matching.yaml,.yml, and.json files in repositories. Security analysis flags weakened authentication, and schema scans identify new or changed fields such as SSNs, credit-card numbers, and passports with GDPR/CCPA warnings. YAML rules in.coderifts.yml can block merges over limits, deprecation, or authentication requirements. Integrations include GitHub App, GitHub Actions, GitLab CI, Bitbucket Pipelines, REST API, CLI, and an MCP server with three tools. Specifications are processed in memory and discarded; derived verdicts and metadata remain. Plans are Free at free, Team at $149 a month, and Enterprise at $1,500 a month.

Zally is an API linter and quality assurance tool for OpenAPI specifications. It supports OpenAPI 3 and Swagger OpenAPI 2, with a RESTful API, command-line interface, and web interface. Its standard configuration checks APIs against Zalando’s RESTful Guidelines, and the project says it can also be used out of the box by others. Teams can enable or disable server-side rules, configure some existing rules, or implement their own in Kotlin. An API definition can use the x-zally-ignore extension to disable rules for that API. The web interface lists implemented rules and can lint external files and API definitions in its online editor. The project describes starting the web UI, server, and database together using Docker Compose. It also lists an unofficial Zally Maven Plugin integration. Maintained by Zalando, Zally is offered under an MIT license with an exception. Its Open source plan costs nothing.