licensecompat checker

Eclipse Public License 2.0 (EPL-2.0)

Module-level copyleft. GPL-incompatible BY DEFAULT (the EPL-2.0 secondary-license option can be set to GPL by the original author, but assume incompatible unless explicitly designated).

Key facts

SPDX id
EPL-2.0
Category
Weak copyleft
Copyleft scope
module
Express patent grant
Yes
SaaS triggers disclosure
No
GPL-compatible
No (by default) — incompatible unless the author designated GPL as a secondary license.

Obligations

When redistributing as open source.

Internal use only (never distributed)

  • EPL-2.0: retain the copyright notice and license text.
  • EPL-2.0: state significant changes made to the code.

Public SaaS / hosted web service

  • EPL-2.0: retain the copyright notice and license text.
  • EPL-2.0: state significant changes made to the code.

Commercial use

Yes. Copyleft is scoped to modified EPL-2.0 modules — your own modules can stay proprietary. Disclose modified modules when you distribute.

Permissive: include notices (Apache also needs NOTICE + change statements). Weak copyleft: disclose only the modified library/files and, for LGPL static linking, provide a relink path. Strong copyleft (GPL): NOT possible to keep proprietary if GPL code is in the derivative work. AGPL: same as GPL plus network rules.

FAQ

Can I use EPL-2.0 in a commercial product?
Yes. Copyleft is scoped to modified EPL-2.0 modules — your own modules can stay proprietary. Disclose modified modules when you distribute.
Do I have to open-source my code if I use EPL-2.0?
Only modified EPL-2.0 modules, and only when you distribute. Your own modules are not affected.
Does running EPL-2.0 software as a SaaS require source disclosure?
No. Hosting is not distribution under EPL-2.0; running it as a service does not trigger source disclosure.
Is EPL-2.0 compatible with the GPL?
No (by default) — incompatible unless the author designated GPL as a secondary license.

Compatibility with other licenses

Open the checker with EPL-2.0 selected