Can I use EPL-2.0 code in proprietary software?

Short answer: 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.

Shipping EPL-2.0 code in a commercial product: Yes

License: Eclipse Public License 2.0 (EPL-2.0, curated)

• Every use you described is granted by EPL 2.0, and nothing you described is prohibited.

Duties: license_notice, share_alike, source_disclosure

Shipping modified EPL-2.0 files: Yes

License: Eclipse Public License 2.0 (EPL-2.0, curated)

• Every use you described is granted by EPL 2.0, and nothing you described is prohibited.

Duties: license_notice, share_alike, source_disclosure

Context

• Source for modified EPL files must be made available; a Secondary License notice can allow GPL compatibility.

Sources

• Eclipse Public License 2.0
• EPL-2.0 FAQ

Check it yourself (free, no key)

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

Computed from Rightshold's license profiles; not legal advice. Updated 2026-10-23. JSON · Markdown