A GitHub App that checks OpenAPI 3.x JSON or YAML contracts on every pull request and posts a native GitHub Check. It catches removed endpoints, responses, required inputs, and incompatible schema changes before merge—without adding a workflow file. Founding Starter offer: £1 for the first month, then £19/month.
No reviews yetBe the first to leave a review for API Contract Guard
Maker
📌
I built API Contract Guard after seeing API compatibility checks treated as a manual release task. Install the GitHub App, open a pull request that changes an OpenAPI file, and the result appears directly in GitHub Checks—no workflow file or sales call. There is a live proof pull request and a £1 first-month founding offer. I would especially value feedback from teams maintaining public or internal APIs.
Report
Installed it on a side repo last night and was surprised the check actually flagged a renamed query param our team had missed for weeks. No workflow file is a nice touch.
Report
Maker
@emirdemirbwv23 Yes I felt like it was a much better "drop in" experience just using the GitHub app
Any other opinions, suggestions or complaints are welcome :)
Report
Installed it on a small Express repo and it caught a removed response field before I even refreshed the PR view. The native Check Run fits right into the review flow, no extra workflow noise.
Report
Love that it runs as a native GitHub Check with no workflow file to maintain. Honestly that's the kind of detail that wins over backend teams who'd otherwise ignore yet another tool.
Report
Installed it on a side project yesterday and the PR check popped up within seconds, flagging a removed response field I would have shipped to prod. Native check integration is genuinely useful, no extra yaml in the repo is a nice touch.
Report
One thing I'd love is a "breaking change severity" label on the GitHub Check, like minor vs major, so reviewers can triage PRs faster. Right now the check tells me something changed but not how much it might hurt downstream consumers.
Installed it on a side repo last night and was surprised the check actually flagged a renamed query param our team had missed for weeks. No workflow file is a nice touch.
@emirdemirbwv23 Yes I felt like it was a much better "drop in" experience just using the GitHub app
Any other opinions, suggestions or complaints are welcome :)
Installed it on a small Express repo and it caught a removed response field before I even refreshed the PR view. The native Check Run fits right into the review flow, no extra workflow noise.
Love that it runs as a native GitHub Check with no workflow file to maintain. Honestly that's the kind of detail that wins over backend teams who'd otherwise ignore yet another tool.
Installed it on a side project yesterday and the PR check popped up within seconds, flagging a removed response field I would have shipped to prod. Native check integration is genuinely useful, no extra yaml in the repo is a nice touch.
One thing I'd love is a "breaking change severity" label on the GitHub Check, like minor vs major, so reviewers can triage PRs faster. Right now the check tells me something changed but not how much it might hurt downstream consumers.