GNU Lesser General Public License v2.1, explained

Weak copyleft LGPL-2.1-only · LGPL-2.1-or-later

LGPL-2.1 lets you use a library from closed-source software, provided users can replace the library with a modified version; changes to the library itself must stay under the LGPL.

Not legal advice. Read the licence text for the exact terms.

What it allows

  • Link the library from closed-source software
  • Use it commercially

What it requires

  • Share changes to the library itself under the LGPL, with source
  • Let users relink your program with a modified version of the library (simple with dynamic linking; with static linking, provide object files)
  • Keep notices and include the licence
  • Do not prohibit reverse engineering needed to debug such changes

When it matters

Shipping an appUsually fine with dynamic linking (a separate shared library, a separate npm or PyPI package). Bundling or static linking needs more care.
A hosted service (SaaS)No obligation while you do not distribute the code.
Internal useNo 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.

Questions

Is LGPL safe for proprietary software?

Generally yes when the library stays a separate, replaceable component and you share changes to the library itself.

Other licences

Published ; awaiting review.