Open Source Software Compliance
Open source software compliance means honouring the conditions of the copyright licences attached to every component you use. The key risks come from copyleft licences, especially the AGPL for hosted services, gaps found in M&A code scans, unmanaged contributions and AI coding tools. SBOMs, scanning and clear policies keep the risk under control.

Key takeaways
- Open source licences are copyright licences with conditions.
- Permissive licences mainly require notices; copyleft licences can require source disclosure.
- AGPL section 13 extends source obligations to remote network users of modified versions.
- SBOMs support both licence compliance and vulnerability response.
- Code scans in M&A diligence often lead to indemnities or remediation covenants.
- AI coding tools need approved-tool policies and scanning of generated code.
Why open source software compliance matters
Almost every software product, and most internal systems, now include open source components. Open source accelerates development, but each component comes with a licence, and those licences impose conditions. Ignoring them can lead to copyright infringement claims, forced disclosure of proprietary source code, broken customer commitments, failed security reviews and price reductions or indemnity claims in transactions. Open source software compliance is therefore a core part of managing intellectual property and technology risk, not just a developer concern.

This insight explains the main licence types, the AGPL's network use condition, software bills of materials, common findings in M&A diligence, contributor agreements and policies for AI coding tools. It is general information, not legal advice.
The legal basis: copyright licences
Open source licences are copyright licences. Software is protected by copyright in Canada, and the licence grants permission to use, modify and distribute it on conditions. If a user does not comply with the conditions, it may be outside the scope of the licence and exposed to an infringement claim, and some licences terminate automatically on breach, subject to cure provisions. The Open Source Definition maintained by the Open Source Initiative sets out the criteria that a licence must meet to be considered open source, including free redistribution, access to source code, permission for derived works and no discrimination against persons, groups or fields of endeavour. Within that framework, licences vary widely in the obligations they impose.
Permissive versus copyleft licences
Licences fall broadly into two families. Permissive licences, such as the MIT, BSD and Apache 2.0 licences, allow use in proprietary products with relatively light conditions, typically preserving copyright and licence notices and, for Apache 2.0, providing notice of changes and including the patent licence terms. Copyleft licences require that derivative works, or in some cases the combined work, be licensed under the same terms when distributed, with source code made available.
Within copyleft, there are degrees. Weak copyleft licences, such as the LGPL and the Mozilla Public License, generally limit reciprocal obligations to the licensed component or files, allowing linking with proprietary code under conditions. Strong copyleft licences, such as the GPL, extend obligations to the whole program that incorporates the licensed code when it is conveyed. Under the GPL version 3, conveying object code requires conveying the corresponding source code in one of the ways the licence specifies.
| Licence family | Examples | Key obligations | Typical risk for proprietary products |
|---|---|---|---|
| Permissive | MIT, BSD, Apache 2.0 | Notices, attribution, patent terms (Apache) | Low, if notices are maintained |
| Weak copyleft | LGPL, MPL 2.0 | Source for modified component files; linking conditions | Moderate; depends on how the component is integrated |
| Strong copyleft | GPL v2, GPL v3 | Source for the combined work when distributed | High for distributed products |
| Network copyleft | AGPL v3 | Source offered to remote users of modified versions | High for SaaS and hosted services |
| Source-available | Various non-OSI licences | Field-of-use or commercial restrictions | Varies; often restricts competing services |
The AGPL and network use
Traditional copyleft obligations are triggered by distribution, which is why software-as-a-service businesses historically faced less exposure: running GPL software on your own servers is generally not conveying it. The GNU Affero General Public License closes that gap. Section 13 of the AGPL version 3 provides that if you modify the program, your modified version must prominently offer all users interacting with it remotely through a computer network an opportunity to receive the corresponding source of your version, from a network server at no charge. For SaaS companies, an AGPL component that has been modified and is exposed to users over a network can therefore create an obligation to release source code. Many companies prohibit AGPL components in their products or require legal review before use.
Source-available and changing licences
Some popular projects have moved from open source licences to source-available licences that restrict commercial use, particularly offering the software as a competing managed service. These licences do not meet the Open Source Definition and should not be treated as open source in policies. Companies should monitor licence changes in critical dependencies, since a new version may be released under different terms, and should decide whether to stay on an earlier version, adopt a community fork, purchase a commercial licence or replace the component. Contract terms with customers that promise open source components should also be checked whenever a dependency's licence changes.
Software bills of materials
A software bill of materials, or SBOM, is a structured inventory of the components in a piece of software, including open source and third-party code. In the United States, the National Telecommunications and Information Administration published minimum elements for an SBOM on 12 July 2021, as directed by Executive Order 14028 on improving cybersecurity. SBOMs serve both licence compliance and security: they make it possible to identify which products contain a vulnerable component when a new vulnerability is disclosed, and which licences apply. Standard formats, such as SPDX and CycloneDX, allow SBOMs to be generated by tools and exchanged with customers.
Canadian companies selling software to US federal agencies, critical infrastructure operators and large enterprises increasingly receive SBOM requests in procurement. Under Canada's new critical cyber systems framework, designated operators must manage supply chain and third-party product risks, which is likely to increase demand for SBOMs from their suppliers as well.
Building an open source compliance program
An effective program for open source software compliance has a few core elements. A written policy defines approved, restricted and prohibited licences, and the approval process for exceptions. Automated software composition analysis tools scan code repositories and build pipelines to identify components and licences. A review process escalates restricted licences, such as strong copyleft or AGPL, for legal and architectural assessment. Notice files and attribution are generated for each release. Distribution obligations, including source code offers, are met for copyleft components. And training helps developers understand why the rules exist and how to request an exception quickly.
The program should also cover how open source is used, not just what is used. The same component can carry very different risk depending on whether it is used internally, linked dynamically, modified, distributed in an application, embedded in a device or exposed as a service.
Run software composition analysis in your build pipeline, not only before a transaction. Remediation is far cheaper when a problematic component is flagged at the time it is introduced than when it is discovered by a buyer's diligence team months before closing.
Who owns open source software compliance
Open source software compliance works best when ownership is clear. Many companies establish an open source program office or a cross-functional committee with engineering, legal, security and product representatives. Engineering owns tooling and day-to-day decisions within policy; legal owns licence interpretation, exceptions and customer commitments; security owns vulnerability response using the same component inventory. Executive sponsorship matters because remediation can compete with product deadlines. Metrics such as the number of unreviewed restricted licences, the age of open findings and the share of releases shipped with complete notice files help leadership see whether open source software compliance is improving or drifting.
M&A diligence findings
In technology transactions, open source software compliance is tested directly: buyers routinely commission code scans of the target's software. Common findings include missing attribution and notice files, copyleft components linked into proprietary code in ways that create disclosure risk, AGPL components in hosted services, components under licences that prohibit commercial use, outdated components with known vulnerabilities, and code copied from public sources without licence information. Findings do not always derail a deal, but they can lead to specific indemnities, escrow or holdbacks, pre-closing remediation covenants, price adjustments or representations about open source use. Sellers who scan and remediate before going to market avoid surprises and improve their negotiating position. See our mergers and acquisitions practice.
Contributor agreements and outbound open source
Companies that release their own open source projects or contribute to others need policies for outbound activity. Contributions by employees may involve company IP and should be approved, particularly where they could include confidential information or patents. Projects often require contributors to sign a contributor licence agreement, which grants the project licences or assignments for contributions, or to certify a Developer Certificate of Origin, under which the contributor certifies that it has the right to submit the contribution under the project's licence. Companies should review contributor licence agreements before employees sign them on the company's behalf, and should choose the licence and contribution model for their own projects deliberately.
Policies for AI coding tools
AI coding assistants generate code suggestions based on models trained on large amounts of public code, much of it under open source licences. This raises several compliance questions. Suggestions may occasionally reproduce substantial portions of licensed code without the accompanying licence or attribution. The ownership and protectability of AI-generated code is uncertain. Prompts and code sent to an AI service may expose proprietary source code. And AI-generated code may introduce vulnerabilities or outdated dependencies.
Policies should require use of approved tools, ideally enterprise versions with commitments not to train on customer code and with filters that block suggestions matching public code. They should require developers to review and test AI-generated code like any other code, run it through the same composition analysis and security scanning, and avoid entering confidential code into unapproved tools. Some companies track which code was AI-assisted to support later diligence. See our insight on generative AI policies.
Customer contracts and warranties
Customers, especially in regulated industries and government, increasingly ask for representations about open source use: that the software does not include components that would require disclosure of the customer's code, that the vendor complies with all licences, that an SBOM will be provided, and that the vendor will remediate vulnerabilities in components. Vendors should align these commitments with their actual compliance capabilities, and customers should ask for them where the risk warrants. See our insight on AI vendor contracts for related issues in AI procurement.
Open source software compliance checklist
- Adopt a written policy with approved, restricted and prohibited licences.
- Run software composition analysis in development pipelines.
- Generate SBOMs and notice files for each release.
- Review copyleft and AGPL use against distribution and hosting models.
- Monitor licence changes in critical dependencies.
- Govern outbound contributions and contributor agreements.
- Set rules for AI coding tools and scan AI-generated code.
- Prepare for diligence with a remediation plan and documentation.
How TRW & Co helps
We help software companies, their investors and their customers with open source software compliance, including policies, licence analysis, remediation strategies, SBOM and procurement terms, contributor agreements, AI coding tool policies and transaction diligence. See our copyright and trade secrets and technology transactions pages or contact us.
Frequently asked questions
Can we use open source in a proprietary product?
Usually yes, especially under permissive licences, provided notices and other conditions are met. Copyleft components require careful review because distribution may trigger obligations to release source code.
Why do SaaS companies worry about the AGPL?
Section 13 of the AGPL v3 requires a modified version to offer its source code to users interacting with it remotely over a network, so hosting a modified AGPL component can create disclosure obligations.
What is an SBOM?
A software bill of materials listing the components in a product. The US NTIA published minimum elements in July 2021, and SBOMs are increasingly requested in procurement for both licence and security reasons.
What do buyers look for in diligence?
Missing notices, copyleft components linked with proprietary code, AGPL use in hosted services, restricted licences and vulnerable outdated components. Findings can lead to indemnities, escrows or remediation covenants.
Do AI coding tools create open source risks?
They can reproduce licensed code without attribution and raise ownership questions. Use approved enterprise tools with public-code filters and run generated code through normal scanning and review.
Sources
General information only, not legal advice. References to statutes, courts and authorities describe published law and practice at the date shown.


