Claude - API koruması, Claude/OpenAI SDK kırılma değişikliklerini yakalayan bir CI kontrolü

A GitHub Action that scans your codebase for usage of the Claude/Anthropic and OpenAI APIs that's broken, or about to break, because of a known, dated API change — and auto-fixes the mechanical ones. It keeps its own rule set current by reading each provider's official release notes on a schedule and extracting new breaking changes with an LLM, so it doesn't go stale the way a hand-maintained list would.

LLM provider SDKs change fast, and "it worked last month" is not the same as "it still works." A sampling parameter gets removed, an HTTP client gets swapped, a response shape gets renamed — and the first anyone hears about it is a production error, not a changelog. This tool is meant to be the thing that catches that in CI, before it ships.

Where it's strongest right now, and where it's headed: claude-api-guard started as, and is still deepest on, Anthropic's Claude API — every rule is validated against real downstream code (not just written and assumed correct; see the engineering log below for the actual false positives found and fixed), and its rule set updates itself from Anthropic's live release notes. OpenAI support followed the same bar: hand-extracted from OpenAI's own changelog and migration guides, then fully triaged against a large real codebase (litellm) until every finding checked out.

The plan from here is to keep expanding provider coverage outward from that same foundation — this is meant to grow into a broader "breaking-change guard for every API your project depends on" tool, not stay a single-provider niche script. The "provider" field already built into every rule, and the per-provider PROVIDERS config in sync_rules.py , exist specifically so adding the next provider is a matter of writing its rules and its changelog parser, not restructuring the tool.

No API key needed to use it. Scanning your code costs nothing and calls no LLM at runtime — every rule ships pre-baked in this repo. An Anthropic API key is only used on this repo's own maintenance side, to power the weekly job that reads provider release notes and proposes new rules (every proposed rule still goes through a human-reviewed PR before it's live — see "Rule sync" below).

Add this to a workflow file in the repo you want to protect (e.g. .github/workflows/claude-api-guard.yml ):

That's it — no secrets, no config file, no signup.