Adding Open Source bits to your app is usually a piece of cake, but making sure you don’t step on any license landmines? That’s a whole different story. Depending on how you’re using the code (SaaS vs. shipping a binary, tweaking it or just pulling it in, mixing it with other libraries, etc.) different license conditions may kick in. Sometimes those conditions clash, and suddenly your whole distribution could be illegal, especially when you’ve got dozens – or even hundreds – of Open Source components tucked into the build.
We’ve built a simple license-model language that boils down the crazy variety of Open Source licenses into a handful of clear‑cut, machine-computable permissions and conditions. On top of that we’ve made a tool that asks you what you actually need (e.g., can you ship source? Can you disclose changes? …), then spits out:
* a to‑do checklist of the license conditions you must meet,
* a warning about any possible license incompatibilities among the components you picked, and
* a list of sensible outbound‑license options for your final product.
In short, we turn the headache of Open Source compliance into a quick, automated sanity check, so you can keep building without worrying about walking on a legal minefield.
