DEVELOPMENT VERSION: This is an experimental DALICC environment. Features, data and APIs may change or be reset without notice. A stable version of this service, with a potentially different feature set, will be made available soon at dalicc.net.

2026

GitHub License Compatibility Checker

Enter a public GitHub repository and DALICC finds the packages it depends on and the license of each. By default it reads the repository itself: its dependency files, the libraries its code imports and the install commands in its documentation, so a repository without a manifest file can be checked too. For a repository that declares every dependency in a manifest file, you can ask libraries.io instead.

The licenses DALICC has records for are then checked against each other, the same check the License Compatibility Checker runs on a bundle you put together. DALICC also checks whether the combined work may be published under a target license. When the repository declares exactly one license, DALICC uses it as the target unless you choose another.

DALICC checks licenses against their models and does not replace legal advice. For a decision that matters, ask a lawyer.

Enter a repository as owner/name, for example psf/requests, or paste its address, for example https://github.com/psf/requests.

How should DALICC find the dependencies?

DALICC downloads the code at its latest commit and reads the dependency files, the libraries the code imports, and install commands in its documentation. Works without a manifest file.

For repositories that declare every dependency in a manifest file such as requirements.txt or package.json. libraries.io's copy of a repository can be several weeks old.

The repository's own license is the one it declares. Reading the repository, DALICC looks at GitHub's license detection, the dependency files, the names of the license files, SPDX tags in the code and the README; libraries.io reports the license of its copy. When that is exactly one license DALICC has, it is the target. Otherwise the check runs without one and the answer says why.

The license you would publish the combined work under. DALICC then checks the dependency licenses against it as well as against each other. Licenses created with the License Composer are unlisted: to use one, enter its identifier.

Reading the repository sends its owner and name, and the branch, tag or commit you give, to GitHub, and the names and versions of the packages it finds to deps.dev, the Python Package Index and the npm registry. Asking libraries.io sends the owner and name to libraries.io. Nothing about you goes with them. Privacy notice.