Open-source software is part of almost every application your organization deploys, manages, and renews. Black Duck’s 2026 Open Source Security and Risk Analysis (OSSRA)1 report found open source in 98% of the 947 commercial codebases it audited across 17 industries. Every one of those components ships with a license, and open-source licenses carry obligations that never appear on an invoice or in an entitlement record.
For ITAM and SAM professionals, that creates a governance gap. You track commercial licenses, monitor usage, and prepare for vendor audits, yet open-source licenses sit outside that process in most organizations. This guide, part of our software license management series, explains the license types, the compliance risks, and how to bring open source under your SAM program.
TL;DR
- Every open-source component ships with a license, and its obligations never show up in standard entitlement records.
- Open-source licenses fall into two main categories: permissive licenses with a light compliance burden, and copyleft licenses that can require source code disclosure.
- Most obligations trigger when you distribute software, so your risk depends on how you use each component.
- Projects can change their license, so terms need ongoing monitoring.
- AI-generated code and regulation, such as the EU Cyber Resilience Act, add to the compliance workload.
- Organizations that extend their SAM practices to open source will be better prepared for audits, renewals, and regulation.
What are open-source licenses?
Every open-source component ships with a license. That license defines what your organization can do with the code: how you can use, modify, and distribute it. Open source means the source code is available, and the license sets the terms for using it.
Open-source licenses work differently from commercial software licenses. There’s no vendor invoice, no entitlement record, and no renewal date. The obligations sit in the license text bundled with the component, and they apply whether or not anyone in your organization has read it. A single application can carry dozens of them through its dependencies.
The scale explains why this matters. Sonatype’s 2026 State of the Software Supply Chain report2 counts 9.8 trillion open-source downloads, up 67% year over year, across the four largest registries. Harvard Business School researchers estimate that companies would spend 3.5 times more on software without open source, a demand-side value of $8.8 trillion3. Your teams use that value every day, and each use comes with terms.
Where the risk sits
Most open-source obligations trigger when you distribute software, meaning you share it outside your organization. Teams that run unmodified open-source software internally carry light obligations. The exposure grows when your organization builds products, ships software to customers, or hosts modified code as a service. That’s why license tracking works best as a joint effort between SAM, legal, and engineering.
The two categories of open-source licenses
Most open-source licenses fall into two groups, and the distinction between them is the most important thing to understand when you assess risk.

Open-source licenses on a spectrum of obligation:
Permissive licenses
Permissive licenses carry minimal obligations. The most common are MIT, Apache 2.0, and BSD. They generally ask for one thing: keep the copyright notice and license text intact when you redistribute the software. Apache 2.0 also includes an explicit patent grant, which adds legal protection.
Permissive licenses still lead the field. RedMonk’s analysis of GitHub Archive data4 puts them at 73% in 2025, down from a high of 82% in 2022, although RedMonk notes the dip may reflect sampling. For enterprise IT teams, permissive licenses carry a low compliance burden. You still maintain attribution, but there’s no risk of being forced to disclose your own source code.
Copyleft licenses
Copyleft licenses are where compliance risk concentrates. The GPL family, including GPL v2, GPL v3, LGPL, and AGPL, requires that derivative works be distributed under the same license terms.
If your organization modifies GPL-licensed code and distributes the result, you may have to release your own source code under the GPL. For a company that has spent years building proprietary software, that’s a serious intellectual property risk, and it doesn’t take much to trigger it. A developer pulls a GPL library into a project on a Friday afternoon, and the next release carries obligations nobody reviewed.
AGPL adds a network clause. If you modify AGPL-licensed software and let users interact with it over a network, such as in a SaaS application, you must offer those users the source code of your modified version, even though you never ship a binary. That catches many teams off guard.
Quick comparison of major open-source licenses
Comparison of major open-source licenses by risk, obligations, and patent grant

This table is general information, not legal advice. Review the exact license terms with your legal team.
Why open-source license compliance matters for enterprises
Open source forms the foundation of modern software, and compliance gaps follow it. Black Duck’s 2026 OSSRA report found license conflicts in 68% of audited codebases, the highest rate in the report’s history and up from 56% the year before. A license conflict means an application combines components with incompatible license terms.
The inventory problem is growing too. The average number of open-source components per codebase rose 30% year over year, and 17% of components enter codebases outside traditional package managers, so manifest-based scanning can miss them. Some components carry no detectable license or use custom terms that need individual legal review. That’s arguably worse than a known conflict, because you can’t comply with obligations you can’t identify.
The consequences of getting this wrong are concrete:
- Legal action from copyright holders. Organizations such as the Software Freedom Conservancy5 (SFC) actively enforce GPL compliance. SFC has been in litigation against Vizio since October 2021, arguing that a consumer can enforce the GPL’s source code obligations as a third-party beneficiary. SFC lists the trial as expected in late 2026.
- Forced source code disclosure. A copyleft violation may require you to release proprietary code under an open-source license.
- M&A complications. Open-source license issues regularly surface during due diligence, and unresolved conflicts can delay or devalue an acquisition.
- Audit exposure. As software audits expand beyond traditional vendor compliance, organizations without open-source visibility face a growing blind spot.
The regulatory dimension
The regulatory side adds urgency. The EU Cyber Resilience Act (CRA)6 applies to manufacturers of products with digital elements sold in the EU. Its reporting obligations for actively exploited vulnerabilities and severe incidents began on September 11, 2026. Full application follows on December 11, 2027, including the requirement to document a product’s components in a machine-readable SBOM that covers at least its top-level dependencies. Manufacturers keep the SBOM in their technical documentation and give it to market surveillance authorities on request.
EU Cyber Resilience Act timeline
The stakes are high. Non-compliance with the CRA’s essential cybersecurity requirements can draw administrative fines of up to €15 million or 2.5% of worldwide annual turnover, whichever is higher. The regulation exempts open-source software stewards from fines, so the exposure sits with the manufacturers who build on their code.

The CRA’s SBOM duty serves vulnerability handling, but the same component list gives you the starting point for a license review. Organizations are already moving. ENISA’s 2026 SBOM adoption survey7 of 334 organizations found that only 10% don’t generate SBOMs at all, and 43% say the CRA significantly accelerated their SBOM tooling and automation investment. Yet only 22% use SBOM data to verify that open-source licenses are properly used and declared. Most organizations already have the component list. Few put it to work on license compliance.
The rising complexity of software licensing
Open-source licensing used to be relatively stable. A project chose a license and kept it. Since 2021, several major projects have changed course, and that has caught many IT teams flat-footed.
Source-available vs. open source
Several well-known projects have moved from open-source licenses to restrictive “source-available” terms, and some have moved again since:
- Elastic (Elasticsearch, Kibana) moved from Apache 2.0 to SSPL and the Elastic License in 2021, then added AGPL as an option in August 2024.
- HashiCorp (Terraform, Vault, Consul) moved from MPL 2.0 to the Business Source License (BSL 1.1) in 2023.
- Redis moved from BSD to a dual RSALv2 and SSPLv1 license in March 2024, then released Redis 8 under AGPLv3 in May 2025.
Source-available licenses look like open source at first glance because the code is publicly visible. They restrict commercial use, competitive use, or managed-service offerings. An organization that deployed Redis under BSD may have found itself under different terms after March 2024, and the terms changed again in 2025.
The community also responds to relicensing. After the Redis change, the Linux Foundation backed Valkey, a BSD-licensed fork supported by companies such as AWS, Google, and Oracle. For SAM teams, a fork can mean a migration project, so a relicensing event has a cost even when you decide to stay on the original.
SAM teams know this pattern from Oracle Java, where changing terms left organizations exposed in ways their original deployments never anticipated. Open-source licenses can change in the same way, so tracking them calls for ongoing monitoring.
AI-generated code and licensing uncertainty
AI coding assistants add another layer of complexity. Black Duck’s 2026 OSSRA report links part of the rise in license conflicts to what it calls “license laundering,” where assistants generate snippets derived from copyleft sources without keeping the original license information, according to SD Times8. Governance hasn’t caught up. Black Duck research cited alongside the report found that 76% of surveyed organizations check AI-generated code for security risks, but only 54% evaluate it for IP and license risks, and just 24% apply comprehensive IP, license, security, and quality evaluations. The legal questions around AI-generated code remain open.
“Open weights” AI models raise a related question. The Open Source Initiative published its Open Source AI Definition 1.0 in October 2024, and in February 2025 it said that Meta’s Llama 3.x license9 doesn’t meet the Open Source Definition because it restricts how you can use the model.
For SAM teams, AI-generated code and AI model deployments belong in the license tracking conversation, even where the obligations aren’t fully settled. Waiting for the legal picture to settle doesn’t remove obligations that already exist.
How to manage open-source licenses in your software estate
Managing open-source licenses follows the same principles as managing commercial software licenses: visibility, classification, policy, and ongoing monitoring.
Build a complete software inventory
Open-source tracking starts with knowing what’s in your environment. For applications your teams build, a Software Bill of Materials (SBOM) catalogs every component, including libraries, frameworks, and dependencies. Software composition analysis tools generate those SBOMs from code, and they complement your SAM platform. Because 17% of components arrive outside package managers, pair manifest-based scanning with a second method that inspects the code itself.
For the software installed across your devices and servers, automated discovery does the same job at the estate level. Modern estates change constantly, applications pull in hundreds of dependencies, and those dependencies update often. Manual inventory methods can’t keep pace, and a spreadsheet leaves you behind.
Xensam discovers the applications installed across your estate, including open-source applications that never appear in a purchase order or contract. If your discovery tools only track commercially licensed software, you’re missing that layer.
Classify open-source licenses by risk
Once you can see your open-source components, set a classification policy:
- Approved: Permissive licenses (MIT, Apache 2.0, BSD) that carry minimal obligations
- Restricted: Copyleft licenses (GPL, AGPL) that need review before deployment in products or services
- Prohibited: Licenses incompatible with your organization’s distribution model or IP strategy
- Flagged: Source-available licenses (SSPL, BSL) that restrict commercial or competitive use
Document this classification, share it with development teams, and enforce it through your procurement and deployment workflows. Four categories, clear criteria, and a review process for anything that doesn’t fit neatly will catch most of the risk.
Integrate open-source tracking into your SAM program
Open-source obligations belong in the same governance framework as commercial license compliance. That means:
- Including open-source components in your software inventory alongside commercial entitlements
- Adding open-source license checks to your audit preparation process
- Monitoring for license changes when components update, particularly for projects that have relicensed before
- Tracking compliance at the application level, since a single application can combine dozens of open-source licenses
- Putting your SBOM data to work: with only 22% of organizations using SBOMs for license verification, this is the quickest way to get ahead
Treating open source as a separate concern from commercial SAM is how compliance gaps form. The obligations differ in kind, covering attribution and distribution instead of license counts, but the governance need is the same: know what you have, know what it requires, and stay compliant. It helps to treat open source as one more asset type moving through the asset lifecycle, from request to retirement.
Prepare for regulation and standards
Three frameworks shape how organizations manage open-source license compliance:
- EU Cyber Resilience Act (CRA): Binding law for manufacturers of products with digital elements sold in the EU. Reporting obligations began on September 11, 2026, and SBOM documentation requirements apply from December 11, 2027.
- OpenChain ISO/IEC 523010: The international standard for open-source license compliance programs. It defines the processes, roles, and controls an organization needs to maintain compliance. Adoption is voluntary.
- SPDX (ISO/IEC 5962)11: The ISO-approved standard for documenting license and component information in SBOMs. The CRA doesn’t mandate an SBOM format, and SPDX is one widely used option.
OpenChain and SPDX are voluntary, but they give you a recognized structure for a compliance program and for SBOM documentation. Organizations that build these capabilities now will have a smoother path when the CRA’s full requirements arrive.
Bring open source into your license management
Open-source license management is a growing part of enterprise software governance. Xensam gives you automated discovery across SaaS, on-premises, and cloud environments, so software that no purchase order covers still shows up in your inventory. Explore the rest of our software license management guides, or book a demo to see it in your own environment.
FAQ
What’s the difference between permissive and copyleft licenses?
Permissive licenses, such as MIT and Apache 2.0, let you use, modify, and distribute the software with minimal requirements, typically just retaining the copyright notice. Copyleft licenses, such as GPL and AGPL, require that derivative works be distributed under the same license terms, which can mean disclosing your own source code.
Can I use GPL-licensed software in commercial products?
Yes, with conditions. If you distribute GPL-licensed code, including a product that incorporates it, you must make the corresponding source code available under the GPL. That can include your own modifications and any derivative work. For internal use with no distribution, the GPL’s obligations generally don’t apply. AGPL adds a network clause: if you modify AGPL software and users interact with it over a network, you must offer them your modified source. Ask your legal team about edge cases, such as sharing software between group companies.
What happens if my organization violates an open-source license?
Consequences range from cease-and-desist notices to lawsuits. Copyright holders can seek injunctions that force you to stop distributing the software or to release your source code. In M&A scenarios, open-source license problems found during due diligence can delay a transaction or reduce its valuation.
Do open-source licenses apply to software used only internally?
They do, but most copyleft obligations trigger on distribution, meaning you share the software outside your organization. Internal use of unmodified GPL software typically doesn’t trigger the copyleft requirement. The AGPL network clause applies when you modify the software and users interact with it remotely. Permissive licenses still ask you to keep attribution notices when you redistribute. Always review the specific terms for each deployment.
What is an SBOM and why does it matter for license compliance?
A Software Bill of Materials (SBOM) is a structured inventory of the components in an application, including open-source libraries, their versions, and their licenses. SBOMs give you the visibility to assess license obligations, find conflicts, and show compliance during audits. The EU Cyber Resilience Act requires manufacturers of products with digital elements to document components in an SBOM from December 11, 2027, which makes SBOMs a regulatory requirement as well as a governance practice.
- https://www.blackduck.com/resources/analyst-reports/open-source-security-risk-analysis.html ↩︎
- https://www.sonatype.com/state-of-the-software-supply-chain/introduction ↩︎
- https://papers.ssrn.com/sol3/papers.cfm?abstract_id=4693148 ↩︎
- https://redmonk.com/sogrady/2026/03/25/open-source-licensing-2026/ ↩︎
- https://sfconservancy.org/ ↩︎
- https://eur-lex.europa.eu/eli/reg/2024/2847/oj ↩︎
- https://www.enisa.europa.eu/sites/default/files/2026-06/SBOM%20Adoption%20State%20of%20Play%202026.pdf ↩︎
- https://sdtimes.com/ai/report-open-source-licensing-conflicts-hit-an-all-time-high-as-organizations-struggle-to-audit-ai-generated-code-for-ip-risks/ ↩︎
- https://opensource.org/blog/metas-llama-license-is-still-not-open-source ↩︎
- https://openchainproject.org/license-compliance ↩︎
- https://spdx.dev/ ↩︎


