Technology

· 4 min read

Open-source code in an acquisition:

what buyers ask for.

Buyers now scan software for open-source licences before they sign. Here is what they look for and how to be ready.

A printed contract with red-pen edits on a pale oak desk, with reading glasses and a cup of coffee

Almost every modern software product contains open-source code, usually a great deal of it. That is normal and rarely a problem. What worries a buyer is not that open source is present but that no one at the company can say exactly where, under which licence, and how it is used. In diligence, that uncertainty is priced in. The following covers what buyers typically ask for.

The inventory

Buyers will ask for a list of components, with versions, licences and where each is used in the product. Software composition analysis tools can produce much of this, and many acquirers run one themselves. A seller who has already done so, and has reviewed the results, begins the conversation from a position of strength.

Why the licence matters

Licences fall into broad families with very different obligations. Permissive licences, such as MIT, BSD and Apache 2.0, generally ask for notices and attribution. Weak copyleft licences, such as the LGPL and MPL, impose conditions on modified files or libraries. Strong copyleft licences, such as the GPL, can require source code to be made available when the covered code is distributed as part of a product. The AGPL extends a similar obligation to software offered over a network.

“The question is rarely which licence the code carries. It is how the code is used.”

How a component is linked, whether it is distributed to customers or run only on your servers, and whether you have changed it all affect the analysis. The answers are technical, so they need engineers and lawyers in the same conversation.

Where problems hide

  • Dependencies of dependencies, which no one chose deliberately.

  • Code copied from forums or sample repositories with no licence at all.

  • Contributions from contractors whose agreements did not assign their work to the company.

  • Code suggested by AI coding tools, whose origin and licence may be unclear and should be covered by a written policy.

What goes in the deal documents

Purchase agreements usually contain representations about the company’s use of open-source software, a disclosure schedule listing exceptions and sometimes a special indemnity for specific identified risks. When an issue is found, the usual solutions are practical: replace the component, rewrite the code, obtain a commercial licence, or change how the product uses it. Buyers tend to accept a credible remediation plan more readily than a company that says there is nothing to find.

Before you go to market

  • Run a composition scan and have someone read the results.

  • Adopt a one-page open-source policy and apply it to new code.

  • Confirm that every contractor and former employee has assigned their work to the company in writing.

  • Fix the high-risk findings first and document the rest.

Arjun Sethi, Partner

Arjun Sethi

Arjun Sethi

Partner ·

Partner ·

IP & Technology

IP & Technology

Software, data and licensing agreements, trade secrets, and biometric privacy (BIPA) compliance and defense.

Create a free website with Framer, the website builder loved by startups, designers and agencies.