Eclipse Public License 2.0 (EPL 2.0)
Ensure that improvements to a component remain open source, without affecting the rest of the project that uses it.
← Back to the 11-license comparison guide
Risk Assessment by Project Type (Proprietary / Commercial)
1. SaaS / Cloud Application (operated by you)
Safe for internal or SaaS use. The constraints only apply in case of distribution.
2. Distributed Software (Dynamic Linking)
CAUTION: You (or your client if they redistribute) must publish modifications made to the files under this license.
3. Distributed / Embedded Software (Static Linking)
CAUTION: You (or your client if they redistribute) must publish modifications made to the files under this license.
4. 100% Internal Tool (Undistributed)
Safe for internal or SaaS use. The constraints only apply in case of distribution.
Philosophy & Ideal Use
- Ensure that improvements to a component remain open source, without affecting the rest of the project that uses it.
Your Main Obligations
- Publish modifications to the files under the EPL.
- Provide the source code of the modified files.
- Does not apply to code that dynamically links to the component.
✓ Permissions
- Commercial use
- Modification
- Distribution
- Private use
- Patent grant
⚠ Conditions
- Share modifications to files under the same (or compatible) license
- Include copyright and license text
✕ Limitations
- No warranty
- Limitation of liability