Check the licences of all your dependencies

Upload or paste your lockfile and say what you are building. We look up the licence of every package version and email you a report: GPL, AGPL, unknown and source-available licences flagged for your kind of project, and explained in plain words. Free, no account. Not legal advice.

or paste its content

The same licence matters differently in an app you ship, a SaaS or an internal tool.

Only package names and versions (and the licences your lockfile declares) are read; the file itself is not kept. Not legal advice. Privacy policy.

How it works

  1. We read the exact versions from your lockfile (and, for npm and Composer, the licence each package declares). The file itself is not kept.
  2. We look up each version's licence on deps.dev, Google's Open Source Insights, which reads what each package declares on its registry. Each version is looked up once for everyone.
  3. Each licence is sorted into a family: permissive, weak copyleft, strong copyleft, network copyleft, source-available or unknown. Expressions like MIT OR Apache-2.0 take the most permissive choice.
  4. The flags depend on your project: GPL matters in an app you ship, AGPL in a SaaS, and almost nothing in a tool that never leaves your company. You get the report by email in a minute.

Copyleft in two minutes

Every open-source licence lets you use the code. They differ in what you owe in return. Permissive licences ask for a notice; copyleft licences ask you to share source code under the same licence, and differ in how far that reaches and what triggers it.

FamilyWhat it asks of youExamples
Public domainThe author gave up their rights as far as the law allows: no conditions to follow.Unlicense, CC0-1.0
PermissiveYou can use, change and ship the code in any product, including closed-source ones. You must keep the copyright and licence notice (usually in a third-party notices file); Apache-2.0 also asks you to state changes and keep its NOTICE file.MIT, MIT-0, Apache-2.0, BSD-2-Clause, BSD-3-Clause
Weak copyleftYou can use the library in a closed-source product, but changes to the library's own files (MPL, EPL) or to the library itself (LGPL) must be shared under the same licence. LGPL also expects users to be able to replace the library, which is simple with dynamic linking and harder with static linking or bundling.LGPL-2.0-only, LGPL-2.1-only, LGPL-3.0-only, MPL-1.1, MPL-2.0
Strong copyleftIf you distribute software that includes or links this code (an installer, a mobile or desktop app, a container image you hand out, JavaScript sent to browsers), the whole combined work must be offered under the same licence, with its source code. Running it only on your own servers is not distribution.GPL-2.0-only, GPL-3.0-only, EUPL-1.1, EUPL-1.2, CECILL-2.1
Network copyleftLike strong copyleft, and more: if users interact with a modified version over a network (a SaaS or a web API), you must offer them its source code. The common case to check is AGPL in a hosted service.AGPL-3.0-only, OSL-3.0
Source-available (not open source)Not an open-source licence: the source is public but use is restricted, typically to stop you offering the software as a hosted service or competing with its publisher. Read the terms before using it in a product.SSPL-1.0, BUSL-1.1, Elastic-2.0, PolyForm-Noncommercial-1.0.0, PolyForm-Small-Business-1.0.0

AGPL and SaaS

The GPL is triggered by distribution: shipping binaries, an installer, a container image you hand out or JavaScript sent to browsers. Running GPL code on your own servers is not distribution. AGPL-3.0 closes that gap: if users interact with a modified version over a network, you must offer them its source code (section 13). That is why AGPL is the licence to look at first in a hosted product, and why some companies ban it outright. Unmodified AGPL software used as a separate program (a database you talk to over its protocol) is a common, more nuanced case: read more about AGPL.

What "no licence" means

No licence is not the same as "free to use". Copyright applies by default, so code published without a licence is "all rights reserved": you have no right to copy, change or ship it. Often the licence exists but is not declared in the package metadata; check the repository for a LICENSE file, and ask the author to add it to the package.

Licence changes to watch

Some projects change licence between versions, most often from an open-source licence to a source-available one (such as SSPL or the Business Source License) that restricts offering the software as a service; a few have moved back. A version you already use keeps the licence it was released under, but an upgrade can bring new terms. The report flags packages whose other versions we know are under a different kind of licence, so you can check before upgrading.

What you get

12 licences to check in package-lock.json

Project: a hosted service (SaaS)

MIT 612 · Apache-2.0 88 · ISC 61 · BSD-3-Clause 24 · …

Look at this first: network copyleft in a hosted service (1)
If users interact with a modified version over a network, you must offer them its source. some-agpl-package 2.1.0: AGPL-3.0-only

Worth checking: no licence found (11)
Code without a licence is "all rights reserved" by default…

Licences, explained

Questions

Is this legal advice?

No. It shows which licences to look at first for your kind of project, and why. Read the licence texts, or ask a lawyer, before making a decision.

Can I use GPL libraries in a commercial app?

You can sell GPL software, but if you distribute an app that includes or links GPL code (desktop, mobile, on-premises, JavaScript sent to browsers), the whole app must be offered under the GPL with its source. Running GPL code only on your own servers is not distribution.

Is LGPL safe for proprietary software?

Generally yes when the library stays a separate component that users could replace (dynamic linking, a separate package), and you share changes made to the library itself.

What does AGPL require for a web service?

If users interact over a network with a modified version of AGPL code, you must offer them its source. It is the licence to check first in a SaaS.

What if a package has no licence?

Code without a licence is "all rights reserved" by default: you have no right to use or ship it. Check its repository for a licence file, or ask the author.

Where do the licences come from?

From deps.dev (Google's Open Source Insights), which reads what each package declares on its registry, and from the lockfile itself where deps.dev has nothing (npm and Composer lockfiles record licences).

Last updated .