Six products will tell you Stripe changed. oxpecker tells you which of your lines it broke — on the pull request, before the sunset date. 68 vendors watched; your source never leaves your CI.
Which vendor has burned you the worst? That's genuinely the roadmap.
About oxpecker on Product Hunt
“Know which of your lines a vendor just broke”
oxpecker launched on Product Hunt on August 14th, 2026 and earned 73 upvotes and 1 comments, placing #19 on the daily leaderboard. Six products will tell you Stripe changed. oxpecker tells you which of your lines it broke — on the pull request, before the sunset date. 68 vendors watched; your source never leaves your CI.
On the analytics side, oxpecker competes within SaaS, Software Engineering and Developer Tools — topics that collectively have 604.1k followers on Product Hunt. The dashboard above tracks how oxpecker performed against the three products that launched closest to it on the same day.
Who hunted oxpecker?
oxpecker was hunted by Ibrahim Chhipa. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of oxpecker including community comment highlights and product details, visit the product overview.
Ibrahim Chhipa
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.