Java License Checker

Paste your pom.xml, Gradle version catalog or build.gradle and see the license of every dependency, with copyleft and missing licenses flagged. You can export the list to CSV or Markdown.

Optional, for the exact versions resolved by Gradle.

Files are processed in your browser. Only package coordinates and versions are sent to the AboutTheApp server, which looks up their licenses in Maven Central and Google Maven.

How the Java license check works

The checker reads the direct dependencies from pom.xml, gradle/libs.versions.toml or build.gradle(.kts) and looks up each artifact's POM in Maven Central and Google Maven: its license, description and project page. When a POM doesn't declare a license, it's taken from the parent POM.

In pom.xml, ${…} properties from the same file are filled in. Versions that come from a parent POM or a BOM, and dynamic Gradle versions, are replaced with the latest stable release. Add gradle.lockfile for the exact versions resolved by Gradle. Test and provided dependencies are left out unless you include them.

Frequently asked questions

How do I list the licenses of Maven dependencies?

Paste pom.xml into the checker. It looks up each dependency's POM in Maven Central, shows its license and lets you export the list to CSV or Markdown.

Does it work with Gradle?

Yes. Paste gradle/libs.versions.toml, the version catalog most Gradle projects use, or a build.gradle(.kts) with dependencies written as group:artifact:version. References to the catalog in build.gradle need the catalog itself.

Is my pom.xml uploaded anywhere?

The file is processed in your browser. Maven Central doesn't allow direct requests from browsers, so the package coordinates and versions go to the AboutTheApp server, which only uses them to look up the licenses.