Global Insights on Open Source Adoption, Risk, and Resilience Trends
Across industries and geographic regions, open source software powers mission-critical applications and is relied upon by organizations of all sizes, from large enterprises to early-stage startups. OSS components comprise the foundation of modern IT infrastructure — and how it is governed, regulated, supported and maintained impacts not just operational resilience for the companies deploying it, but cybersecurity on a global scale.
The 2026 State of Open Source Report offers a comprehensive picture of OSS to help decision-makers shape their adoption strategies and set their teams up for long-term success. In the report, you’ll find insights on the most in-demand open source software, with expert analysis that puts the data into context.
Download the State of Open Source Report today >>
Has your organization increased the use of open source software over the last year?
What is most challenging aboutmanaging Java stacks?
What’s Inside the State of Open Source Report?
Produced in collaboration with the Open Source Initiative (OSI) and the Eclipse Foundation, the State of Open Source Report uncovers areas of maturity, emerging growth opportunities, and shifting attitudes around security, compliance, and digital sovereignty.
This year’s report answers questions such as:
- Is digital autonomy achievable with open source?
- How are new EU regulations like DORA impacting OSS adoption?
- What open source technologies are receiving the most investment?
- Are engineers spending more time on maintenance or feature development?
- Which industries are hosting data on-prem vs. in the cloud?
- What unique challenges are enterprise Java teams facing?
- Are vendor-lock in fears driving a migration off of proprietary tools?
- What percentage of organizations are generating SBOMs?
Who Should Read the State of Open Source Report?
If your job involves open source, you are likely to find valuable information in the State of Open Source Report. The report includes trend analysis that is relevant for:
- Developers and Engineers
- System Administrators
- Architects
- Consultants
- Community Managers
- IT Managers and Directors
- Evangelists/Advocates
- VPs and C-Suite (CEOs, CTOs, CIOs, CISOs, COSOs)
For the following proactive security measures, assign a value of 1 to 5 to indicate its importance:
How much time is spent on maintenance andproduction/bug issues vs. developing new features?
