Back to all posts
Process7 min read·November 8, 2026

Open-Source Licence Checks Before You Ship Commercial Software

TB
ThynkBlox Team
Engineering

Before you ship commercial software, you should know which third-party packages it contains and which licence each one uses. Licences with sharing obligations should go to a lawyer for review, and the required notices should be kept. Repeat the check at every release. None of this needs legal expertise from the founder. It does need a process that someone owns.

This article is a practical checklist, not legal advice. It does not interpret any specific licence. When a question depends on what a licence actually requires, ask a qualified lawyer.

Why does open-source licensing matter to a founder?

Almost every modern product is built on open-source components: frameworks, libraries, utilities and the packages those depend on in turn. Each one comes with a licence that sets out the terms for using it, and those terms differ.

Some licences mainly ask you to keep the copyright and licence notices. Others can attach conditions to how you distribute software that includes the component, such as making related source code available. Whether a condition applies to you can depend on how the component is used and how your product reaches customers.

The commercial risk usually comes from not knowing, rather than from open source as such. The questions tend to arrive at awkward moments: a customer's procurement review, an investor's due diligence, or an acquisition. For a wider view of open source as a choice, see our article on the pros and cons of open-source software.

What does the licence checklist cover?

Use this table as a brief for your development team or build partner.

StepWhat to doWho usually owns it
InventoryList every third-party package, including indirect dependenciesEngineering
Record licencesNote the licence declared for each package and its versionEngineering
Flag for reviewMark licences with sharing obligations, unclear terms or no licenceEngineering, then legal
Legal reviewGet a lawyer to confirm what flagged licences mean for your productFounder and lawyer
Keep noticesGather the attribution and licence texts that need to ship with the productEngineering
Re-check each releaseCompare the new inventory with the last one and review what has changedEngineering, with founder sign-off

Assign a named owner to each step. A checklist without an owner tends to be skipped when a release is under pressure.

How do you build an inventory of third-party packages?

Start from the files your project already uses to declare dependencies. Most programming ecosystems have a manifest and a lock file that records the exact versions installed. The inventory should cover:

  • Direct dependencies that your team chose to add
  • Indirect dependencies pulled in by those packages
  • Code copied into the repository rather than installed as a package
  • Components in container images, mobile builds and deployment scripts
  • Fonts, icons, images and other assets with their own terms

Indirect dependencies are often the largest part of the list and the one most likely to be missed. Ask your team to produce the inventory with an automated tool rather than by hand, so it can be regenerated reliably. Some teams keep this as a software bill of materials, a structured list of components in a build.

Store the inventory alongside the release it describes. When someone asks what was in the version a customer is running, you should be able to answer from a record, not by reconstructing it.

How should you record each licence?

For every package, record at least the name, version, declared licence and where the licence information came from. A simple table or spreadsheet is enough at the start.

FieldWhy it matters
Package and versionLicences can change between versions
Declared licenceThe starting point for any review
Source of the licence informationShows whether it came from package metadata or the licence file itself
How it is usedFor example bundled in the product, used only in development, or run as a separate service
Review statusApproved, flagged, under legal review, or being replaced

Automated scanners are useful but can misread or miss licence information. Treat their output as a first pass, and have someone look at packages where the result is unknown, mixed or inconsistent with the licence file.

Also record how the product is delivered, for example as hosted software, a downloadable application, a mobile app or an on-premises installation. A lawyer will need that context to assess any obligation.

Which licences should go to a lawyer?

Do not ask your developers to decide what a licence means for your business. Their job is to flag, and a lawyer's job is to interpret. Flag a package for legal review when:

  • Its licence includes obligations to share source code or apply the same licence to related work
  • The licence is unfamiliar, custom or restricts commercial use
  • No licence can be found, which does not mean the code is free to use
  • Different files in the package carry different licences
  • The licence information changed in a newer version
  • The package will be modified, or distributed to customers in a new way

Agree in advance on a short list of licences your team may use without review and a list that always needs review. Write it down with your lawyer, then let engineering apply it day to day. Anything outside the lists is flagged by default.

If a flagged package turns out to be a problem, the usual options are to replace it, change how it is used, or accept the obligation knowingly. Make that choice deliberately and record it, for example in an architecture decision record.

What notices do you need to keep?

Many licences ask that copyright and licence notices travel with the software. In practice, teams gather these into a third-party notices file or an "open-source licences" screen inside the product.

Generate the notices from the same inventory you use for review, so they stay consistent. Check that the notices actually ship in every format you distribute, including mobile builds and installers, and that they are not removed during packaging.

Keep copies of the licence texts for the versions you shipped. Projects sometimes move or change licences later, and your record should reflect what applied when you released.

Why check again at each release?

Dependencies change constantly. A routine update can bring in new indirect packages, and a package can change its licence between versions. A clean review last quarter says little about today's build.

Build the check into your release process:

  1. Regenerate the inventory for the release candidate.
  2. Compare it with the previous release and list what is new or changed.
  3. Review any new or changed licences against your approved and review lists.
  4. Hold the release, or record an approved exception, if a flagged item is unresolved.
  5. Regenerate the notices and confirm they are included.
  6. Store the inventory and notices with the release record.

Many teams run the scan automatically in their pipeline so it fails visibly when an unreviewed licence appears. Our guide to CI/CD for founders explains where checks like this sit, and how often to update software dependencies covers the update rhythm that triggers them.

What common mistakes should founders avoid?

Checking only direct dependencies. Most packages come in indirectly, and they carry licences too.

Treating "no licence" as permission. Missing licence information is a reason to flag, not to proceed.

Letting developers interpret licences. Engineers should identify and flag. Legal meaning belongs with a lawyer.

Doing it once before launch. A one-off audit goes stale with the next dependency update.

Forgetting non-code assets. Fonts, icons, images and sample data have their own terms.

Leaving it out of the agency contract. If a partner builds your product, agree that they will deliver the inventory, licence records and notices. Our article on who owns source code in outsourced development covers related contract points.

When does this checklist matter less?

If the software is used only internally and never distributed, some obligations may not apply in the same way. Do not assume that, though. How a licence treats internal use, hosted services and distribution is exactly the kind of question to put to a lawyer. Keeping the inventory still costs little and helps with security and maintenance work, such as an inherited codebase audit.

Frequently asked questions

Do I need a lawyer for every package?

No. Agree on approved and review lists with a lawyer once, let your team apply them, and send only flagged packages for legal review.

Can a scanning tool handle compliance for us?

A scanner speeds up inventory and flagging, but it does not make legal judgements and can misread licence data. Keep a person responsible for reviewing its results.

What should our development partner hand over?

Ask for the dependency inventory, licence records, review decisions, notices file and the process for repeating the check at each release. Include these in the handover checklist.

Is open source a risk we should avoid?

Generally, no. Open source is a normal foundation for commercial software. The aim is to use it knowingly, with records that let you answer questions when they come up.


*Want a build partner that delivers clear dependency and licence records with your software? Start a conversation →*

Ready to build?

Let's turn these ideas into your next product.

Start your project