For you · OSPO
For Open Source Program Offices
If you run an OSPO — or you're the person at your company who owns the open source relationship — BreakPoint is the discovery and handoff layer for projects that are looking for a new maintainer. The 5-move OSPO playbook, applied.
Published July 13, 2026 · ~3 min read
What an OSPO does on BreakPoint
Three things: identify which dependencies are at risk, track the handoff for any projects you adopt or contribute back to, and find new projects to sponsor or adopt as part of your company's open source strategy.
The OSPO playbook
- Inventory the inbound. The first OSPO job is to know what you use. Run a SCA scan (Snyk, GitHub Dependabot, or your language's lockfile tooling), filter to direct + transitive dependencies, and pick the top 20 critical ones. Score each on bus factor.
- Score the bus factor. Use JetBrains Bus Factor Explorer or
git shortlogon the source. A bus factor of 1 + 12 months no release = adoption candidate. - Watch BreakPoint for handoffs. Use the feed filter to watch your top 20 dependencies. When one shows up as "looking for a maintainer," you have a 23-day window to act.
- Sponsor the maintainers. The most cost-effective OSPO intervention is direct sponsorship. Even $100/month changes the calculus.
- Contribute back. One PR a quarter per critical dependency builds bus factor 2+ on the projects you depend on. The 5-move playbook is in the supply chain report.
Frequently asked questions
What does an OSPO do?
Manages the organization's relationship with open source: inbound, outbound, and strategic.
How does BreakPoint help an OSPO?
Identify at-risk deps, track handoffs, find new projects to sponsor or adopt.
How do I get started with OSPO work on BreakPoint?
Sign in, watchlist your top 20, check bus factor on each.