oxpecker

Know which of your lines a vendor just broke

SaaS

Software Engineering

Developer Tools

Visit WebsiteSee on Product Hunt

Hi Product Hunt 👋

I built oxpecker after the third time we learned about an API change from a

customer instead of from the vendor.

The pattern is always the same. A vendor deprecates a field, removes an endpoint,

or makes an optional parameter required. It lands in a changelog nobody

subscribes to, or in no changelog at all. Your code keeps compiling. It breaks in

production, on their schedule.

So we measured it. Across the 30 vendors in our register that publish a

verifiable spec history, there were 917 breaking changes in the last 12 months.

One every 10 hours. Cloudflare alone accounted for 368. We only count changes

that can break a caller, so the 3,386 endpoints added in the same period are

excluded.

oxpecker watches 68 vendors' API specs and tells you which lines in your repo

call the thing that changed. Not "Stripe published an update", but:

src/billing/charge.py:214 calls an endpoint that is going away in March.

It runs as a GitHub Action, and your source never leaves your CI. We resolve the

call sites inside your runner and only ever read the vendor's public spec.

Where we're honest about limits: roughly half the register serves specs with no

public history, so 917 is a floor, not a total. And if your vendor isn't in the

register yet, email [email protected] and we'll add it.

Which vendor has burned you the worst? That's genuinely the roadmap.