Reacting to dissatisfaction in the open source community, Facebook moves React, Jest, Flow, and Immutable.js from BSD + Patents license to the MIT license
Hybrid BSD pact will be replaced by MIT deal for some projects — Faced with growing dissatisfaction about licensing requirements …
Context & Ripple Effects
React has been Facebook's flagship open-source bet since it open-sourced React Native for native iOS apps in 2015, and by 2019 the library was being run by a small full-time team inside the company as part of a portfolio spanning Cassandra, GraphQL, PyTorch, and more (Increment's look at its rise). But the BSD + Patents license attached to React, Jest, Flow, and Immutable.js had become a source of community dissatisfaction, and Facebook is now swapping it for plain MIT.
The move lands in the middle of a broader drift toward permissive licensing: a study of roughly four million packages found 67% relied on permissive licenses like Apache in 2019, up three points. Facebook conceding to community pressure is a notable data point in that shift.
First-order effects
- Companies that had flagged the patent-termination clause as a legal risk can now adopt or keep React, Jest, Flow, and Immutable.js under a standard MIT grant, removing the review burden that made the hybrid BSD pact contentious.
- Facebook trades a defensive legal position for goodwill across its open-source portfolio, protecting adoption of the React ecosystem it depends on.
Second-order effects
- Rival frameworks competing for JavaScript mindshare lose their easiest differentiator — 'no patent clause' — forcing competition back onto developer experience and performance.
- The episode sets a precedent other corporate stewards weigh when choosing licenses: Redis's later switch from 3-clause BSD to a controversial dual-license model shows license terms remain a live competitive lever in both directions.
Third-order effects
- If the pattern holds, large companies treat permissive licensing as table stakes for ecosystem adoption, with restrictive or hybrid terms reserved for cases where they want to control commercialization rather than maximize uptake.
- Community pressure becomes an enforcement mechanism on corporate open-source governance: adoption, not copyright, is the leverage that forces relicensing.
The trend: Corporate open-source stewardship is converging on permissive licenses as communities punish restrictive terms, making license choice a strategic adoption decision rather than a legal afterthought.