It depends.
The compatibility between Beerware License and Eclipse Public License 2.0 depends on the specific clauses and the way the two are combined in your project. Have a qualified lawyer review before redistributing.
| License | Family | Patent grant |
|---|---|---|
| Beerware License (Beerware) | permissive | No (implicit at most) |
| Eclipse Public License 2.0 (EPL-2.0) | weak-copyleft | Yes |
Beerware License: Joke license: 'if we meet someday, you can buy me a beer.' Not legally rigorous.
Eclipse Public License 2.0: Module-level copyleft used heavily in the Java ecosystem.
If you found this page because you're trying to figure out whether shipping a particular dependency is safe, the answer above is a starting point — not a substitute for reading the actual licenses or talking to a lawyer when stakes are high.
LicenseHound walks every transitive dependency in your repo, maps each to its SPDX license, and flags pairs like this one in PR comments. The CLI is free; the team dashboard is paid.