a2ally™ Sign up

MPL 2.0 vs LGPL 3.0: what is the difference?

Last updated

TL;DR: MPL 2.0: commercial use, modification, redistribution: Yes. LGPL 3.0: the same uses: Yes. MPL 2.0: Use, modify and distribute, including in larger proprietary works; files covered by the MPL that you change and distribute must stay under the MPL with their source available. LGPL 3.0: Use the library in any program, including proprietary ones; changes to the library itself, when conveyed, stay under the LGPL with source, and users must be able to relink a modified version.

Is mPL 2.0: commercial use, modification, redistribution allowed under Mozilla Public License 2.0?

Yes. Every use you described is granted by MPL 2.0, and nothing you described is prohibited.

License: Mozilla Public License 2.0 (MPL-2.0, curated)

Duties: license_notice, share_alike, source_disclosure

Is lGPL 3.0: the same uses allowed under GNU Lesser General Public License v3.0?

Yes. Every use you described is granted by LGPL 3.0, and nothing you described is prohibited.

License: GNU Lesser General Public License v3.0 (LGPL-3.0-only, curated)

Duties: attribution, license_notice, share_alike, source_disclosure

How do MPL-2.0 and LGPL-3.0-only compare?

The table lists each license's duties and notes side by side.

LicenseDutiesNotes
MPL-2.0license_notice, share_alike, source_disclosureCopyleft applies file by file. Executable forms may be distributed under different terms if the source of covered files stays available under the MPL (section 3.2); general sublicensing is not documented.
LGPL-3.0-onlyattribution, license_notice, share_alike, source_disclosureThe copyleft duties apply to the library and modified versions of it, not to an application that only links to it.

Combined in one work: compatible.

What else should I know?

What are the sources?

How can I check it myself (free, no key)?

{
  "tool": "check_license",
  "arguments": {
    "license": "MPL-2.0",
    "intended_use": {
      "commercial_use": true,
      "modification": true,
      "redistribution": true
    }
  }
}

Computed from a2ally's license profiles; not legal advice. JSON · Markdown

Get a free API key in one call

No card and no email needed. 100 free credits; the license and policy checks stay free without a key.

curl -s -X POST https://www.a2ally.com/v1/accounts/signup -H "Content-Type: application/json" -d '{"accept_terms":true}'
export A2ALLY_API_KEY=rs_...   # the api_key from the reply (shown once)
curl -s https://www.a2ally.com/v1/licenses/check -H "Authorization: Bearer $A2ALLY_API_KEY" \
  -H "Content-Type: application/json" -d '{"license":"MIT","intended_use":{"commercial_use":true}}'
Get a keyQuickstart