Important infrastructure should not disappear because corporate priorities change. Teams building distributed systems have relied on Spring Cloud Contract for years to keep producers and consumers honest about their API contracts. That reliance doesn't go away when a project's home organization changes course.
Stubborn Contract exists so the project has an independent, long-term home, one that isn't tied to any single company's roadmap. It's led by Marcin Grzejszczak, one of Spring Cloud Contract's original creators, continuing the work he started. He wrote up the full story of this transition on his blog.
Being independent doesn't mean being unstructured. Stubborn Contract is sustained through a combination of open-source collaboration (issues, pull requests, and community feedback) and enterprise investment from organizations that depend on the project in production. That combination is what lets the project stay both open and sustainable, without overpromising a pace of development it can't keep up.
There's also a practical reason this transition works: Marcin didn't just maintain Spring Cloud Contract, he designed it, wrote most of its original architecture, and has carried the context on every non-obvious decision in the codebase since 2016. That continuity of ownership is what makes a clean handoff possible at all, and it's why organizations planning a migration get the most value by working directly with the person who already knows where the edge cases are. You can see that history yourself in the commit log.
The name is a statement of intent: contracts should be verified, not assumed. The project has been stubborn about that idea since the beginning, and stays stubborn about it now.