How to check dependency licences without uploading them
Every dependency you add is a licensing decision, whether it comes from npm, PyPI, crates.io or Go modules — and most of the time that decision is trivial. The trouble starts with the handful that are not: a GPL library in a closed-source product, an AGPL service in a SaaS, an Apache-2.0 library in a GPL-2.0 project. Those are the ones that turn into a relicensing scramble the week before launch, because nobody checked at the time the dependency was added.
This tool checks the decision where the list already is: on your own device. When you paste a list or drop a manifest file here, your browser:
- Reads the licences your file actually declares — package-lock.json carries a licence per package, and name@licence lines state them directly. package.json, requirements.txt, go.mod and Cargo.toml carry no licences at all, so those dependencies are matched against a small built-in snapshot of well-known packages, and flagged Unknown when they are not in it.
- Checks each licence against your project licence — using the compatibility rules the FSF and OSI publish: permissive licences combine freely, weak copyleft (MPL, LGPL, EPL) comes with conditions, strong copyleft (GPL, AGPL) forces the combined work under the same licence. SPDX expressions are honoured: "MIT OR Apache-2.0" takes the best alternative, "MIT AND GPL-3.0" takes the worst part.
- Adjusts for how you ship — internal use does not trigger copyleft, the GPL does not trigger on network use alone, and the AGPL does. A GPL dependency that is Incompatible for a distributed product is Conditional for internal use, and the reason says so.
What makes this checker different
The pages that top the results for this search are mostly pair checkers — pick two licences, get one verdict — or command-line tools you install and run in CI. The dedicated browser tools that do read a manifest are npm-only, or they query a registry from a server, or they produce a licence inventory without ever judging it against your project licence. This page is the only free, fully client-side checker we found that takes a real manifest from five ecosystems, judges every dependency against the licence you actually ship under, explains each verdict in plain English, and hands you a downloadable report — with no install, no account, no upload, and a live network-request counter so you can verify the privacy claim yourself.
When is checking the right choice — and when is it the wrong one?
Checking is right before a release, before adding a new dependency to a commercial product, and before open-sourcing a project that grew in private. It is the wrong choice as a substitute for legal advice: if a verdict affects a shipping decision, a contract, or an acquisition, get a lawyer. It is also the wrong choice for transitive dependencies — this tool checks the list you paste, not the tree underneath it. For a full audit, use a dedicated compliance scanner that resolves the whole tree.
Honest limitations
Guidance, not legal advice
Licence compatibility depends on jurisdiction, exact versions, and how the code is combined. This tool applies the widely accepted rules — it cannot settle an ambiguous case.
Only direct dependencies
The list you paste is what gets checked. A GPL package hiding two levels down in the dependency tree is not seen — resolve the full tree with a compliance scanner for that.
Most manifests carry no licences
package.json, requirements.txt, go.mod and Cargo.toml list names and versions only. Their dependencies are Unknown unless the snapshot knows them or you add name@licence lines.
The snapshot can go stale
Packages get relicensed. A licence marked "snapshot" is a starting point from a small curated list — verify it against the package's own page before relying on it.
Expressions are simplified
Nested SPDX expressions with mixed AND and OR are evaluated conservatively (worst part wins). WITH exceptions are noted, not fully evaluated — read the exception before relying on the verdict.
It never changes your files
This tool only reports and downloads a new report. Your manifest files are never modified — to fix a licence problem, change the dependency or the project licence yourself.