oxpecker catches vendor API breaks in PRs

oxpecker targets the painful gap between vendor changelogs and application impact: knowing a dependency changed is easy; proving what it broke is the valuable part.

• –Maps vendor API changes to specific files and lines in your repository
• –Runs source analysis inside your own CI, keeping code out of the service
• –Opens a pull request with a focused, reviewable change rather than auto-merging fixes
• –Filters harmless vendor updates so teams are interrupted only when their code is affected
• –Its invite-only, 26-vendor coverage makes it promising infrastructure, though breadth and detection accuracy will determine whether it beats internal contract tests