a2ally™ Sign up

MIT vs GPL 3.0: what is the difference?

Last updated

TL;DR: MIT: commercial use, modification, redistribution: Yes. GPL 3.0: the same uses: Yes. MIT: Deal in the software without restriction, including to use, copy, modify, merge, publish, distribute, sublicense and sell it, as long as the copyright and permission notice go with all copies or substantial portions. GPL 3.0: Run, study, change and share the software, including commercially. If you convey it or a work based on it, you must do so under the GPL with the corresponding source.

Is mIT: commercial use, modification, redistribution allowed under MIT License?

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

License: MIT License (MIT, curated)

Duties: attribution, license_notice

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

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

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

Duties: attribution, license_notice, state_changes, share_alike, source_disclosure

How do MIT and GPL-3.0-only compare?

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

LicenseDutiesNotes
MITattribution, license_noticeProvided as is, without warranty.
GPL-3.0-onlyattribution, license_notice, state_changes, share_alike, source_disclosureSublicensing is not allowed; every recipient receives a license from the original licensors (sections 2 and 10). Running the software, including as a network service, does not by itself trigger the duty to share source; conveying copies does.

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": "MIT",
    "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}}'