Can I use EPL-2.0 code in proprietary software?
Last updated
TL;DR: Shipping EPL-2.0 code in a commercial product: Yes. Shipping modified EPL-2.0 files: Yes. The Eclipse Public License 2.0 is a weak, file-level copyleft: changes to EPL files stay EPL, separate modules can carry your own license.
Is shipping EPL-2.0 code in a commercial product allowed under Eclipse Public License 2.0?
Yes. Every use you described is granted by EPL 2.0, and nothing you described is prohibited.
License: Eclipse Public License 2.0 (EPL-2.0, curated)
Duties: license_notice, share_alike, source_disclosure
Is shipping modified EPL-2.0 files allowed under Eclipse Public License 2.0?
Yes. Every use you described is granted by EPL 2.0, and nothing you described is prohibited.
License: Eclipse Public License 2.0 (EPL-2.0, curated)
Duties: license_notice, share_alike, source_disclosure
What else should I know?
- Source for modified EPL files must be made available; a Secondary License notice can allow GPL compatibility.
What are the sources?
How can I check it myself (free, no key)?
{
"tool": "check_license",
"arguments": {
"license": "EPL-2.0",
"intended_use": {
"commercial_use": 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}}'
