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

Tools

Four tools that write or check a license. Two of them produce one, and two of them read a set of licenses and report what stands in the way of using them together.

  • License Composer

    The composer builds a license out of the permissions, prohibitions and duties you switch on. It reasons over the result before you publish it, so a license that contradicts itself is caught while you are still writing it.

    Go to the License Composer

  • Text-to-License

    Paste the text of a license and Text-to-License proposes the machine readable statements behind it. You read every proposal, correct what is wrong and keep the result as your own draft.

    Go to Text-to-License

  • License-to-Text

    Name a license and License-to-Text writes its terms out as a license text in plain English. Every section says which terms of the model it covers, so you can see what the text left out.

    Go to License-to-Text

  • License Compatibility Checker

    Put several licenses into one bundle and the checker says whether they can be used together. It names every conflict it finds and, with a target license, says whether the bundle may be released under that one.

    Go to the License Compatibility Checker

  • GitHub License Compatibility Checker

    Name a public repository and the checker reads the licenses of its dependencies. It maps them onto DALICC records, reports the conflicts between them and, if you name a target license, the conflicts with that one.

    Go to the GitHub License Compatibility Checker

Every check here reasons with a dependency graph, which states how the named actions relate to one another. How reasoning works explains what the tools do with it, and which graph a check follows.