Free tools Windows power users keep installed
One-click scans. No signup required.
The FINOS 2025 Report finds that open source is now a strategic part of financial-services technology, not merely a way to cut software costs. In its survey, 87% of respondents said open source is critical to their organization’s future, and 84% said it is essential to the financial-services sector. The report also highlights a gap between recognizing security risks and putting safeguards such as software bills of materials (SBOMs) into practice.
What is the FINOS 2025 Report?
The 2025 State of Open Source in Financial Services is the fifth annual study from FINOS, produced with Linux Foundation Research, GitHub and Scott Logic. Its 55 pages combine a 2025 survey of 209 respondents, analysis of GitHub activity and qualitative interviews. It examines how banks, fintechs and financial-services vendors use, contribute to and govern open-source software (OSS).
As an Amazon Associate I earn from qualifying purchases.
The findings are respondent and activity-analysis results, not a census of every financial institution. The GitHub analysis may miss contributions made through personal accounts when employers’ policies discourage or restrict work on organizational accounts.
What does the report say open source is worth?
The report presents value as broader than license-cost savings. In the survey, 93% said open source improves software quality. Respondents also associated it with lower software-ownership costs (62%), business value (59%), productivity (58%) and faster time to market (51%). These are respondents’ assessments, not independent measurements of performance across the industry.
#1 Best Overall
Financial institutions also described open source as a way to share the work of developing standards and meeting compliance needs. The practical implication is that value can include quality, delivery speed, resilience, interoperability and skills development, as well as direct savings.
ROI is real for some, but not consistently measured
Eighteen percent of respondents said their organizations were already realizing returns from open source. The Linux Foundation’s summary of the report says nearly one-fifth reported more than $1 million in annual savings. These are distinct reported findings; the summary does not establish that every respondent who reported returns realized savings at that level.
Rank #2
Large organizations reported a mixed picture: among respondents at organizations with more than 10,000 employees, 38% estimated annual OSS savings above $1 million, while 45% said they did not know their savings. That uncertainty makes it difficult to compare savings alone with benefits such as faster delivery or shared standards work.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Are financial firms adopting open source or contributing to it?
Adoption and contribution are different measures. A firm can rely heavily on open-source components without sending code, documentation or other work back to the projects it depends on. The report argues that engagement and collaboration are necessary to realize the full value of open source, rather than treating it only as a source of software to consume.
Rank #3
Half of survey respondents said their organization had a defined open-source strategy. Financial institutions reported higher adoption than fintechs: 55% compared with 38%. In the report’s analysis of observed financial-services open-source contributions on GitHub, Python accounted for about 18%, Java for 7% and C# for 3%. Those figures describe the activity analyzed, not the share of all software written in those languages across the sector.
What security and licensing risks does it identify?
Respondents identified vulnerabilities and supply-chain attacks as leading concerns, but fewer reported a concrete supply-chain practice: actively producing SBOMs.
Rank #4
| Survey finding | Share of respondents |
|---|---|
| Cited vulnerabilities as the leading concern | 52% |
| Cited supply-chain attacks | 37% |
| Reported actively producing SBOMs | 43% |
The figures point to an execution gap: awareness of risk does not by itself establish that an organization can inventory components or manage their provenance. The report recommends stronger supply-chain controls and SBOM practice. It also finds that legal and licensing concerns, like unclear returns on contribution, affect 48% of respondents—an obstacle to contributing as well as a governance issue.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallWhat should a bank or fintech do with the findings?
The report’s practical message is to make open-source use intentional and governed, while creating safe paths for participation. A financial institution can translate that into the following work:
Best Value
- Set an organization-wide strategy. Define who can approve use and contribution, how ownership is assigned, and how teams handle licensing and compliance. An open-source program office (OSPO) or equivalent function can coordinate this governance.
- Make contribution safe and measurable. Establish review and legal pathways for upstream work, then track contributions and outcomes—not only cost avoided, but also delivery, quality, resilience and skills.
- Close the security execution gap. Strengthen software supply-chain controls and build repeatable SBOM processes so teams can identify and manage the components in their software.
- Assess AI and standards work for openness and governance. The report recommends pairing AI investment with deliberate skills development, considering open approaches such as open-weight models, and using responsible-governance frameworks such as the FINOS AI Governance Framework. Evaluate projects for interoperability and vendor neutrality as well as immediate functionality.
How should readers interpret the findings?
The survey reflects a specialist sample of 209 respondents, not every bank, fintech or financial-services vendor. Percentages should be read as reported views and practices among respondents. GitHub activity analysis has a separate limitation: employer policies may lead developers to use personal accounts, leaving some organizational work outside the observed data.
The report’s central distinction is therefore between strategic recognition and operational maturity. Many respondents see open source as critical, but strategy, contribution pathways, savings measurement and security practices are not equally established. For a financial firm, the useful question is not only how much open source it uses, but whether it can govern, secure, measure and responsibly contribute to the software and standards on which it relies.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
