GNU Lesser General Public License v3.0, explained
Weak copyleft LGPL-3.0-only · LGPL-3.0-or-later
LGPL-3.0 is GPL-3.0 with extra permissions: closed-source software may use the library, provided users can replace it and changes to the library itself stay under the LGPL.
Not legal advice. Read the licence text for the exact terms.
What it allows
- Use the library from closed-source software
- Use it commercially
What it requires
- Share changes to the library under the LGPL
- Let users replace the library with a modified version, and, for consumer devices, provide the installation information needed to do so
- Keep notices and include both the GPL and LGPL texts
When it matters
| Shipping an app | Usually fine with dynamic linking. Locked-down devices that prevent replacing the library are a problem under version 3. |
|---|---|
| A hosted service (SaaS) | No obligation while you do not distribute the code. |
| Internal use | No obligation. |
Its family: weak copyleft
You 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.
Other licences
Related free tools
Dependency licence check
Upload a lockfile and see every dependency's licence. GPL, AGPL, unknown and changed licences are flagged for your kind of project. Free.
SBOM summary generator
Upload a lockfile and get an SBOM summary by email: components, licences, vulnerabilities and AI components. CycloneDX and SPDX files with Pro.
Published ; awaiting review.