Terms
Everything here is MIT licensed and provided as-is. The short version: take the code, ship it commercially, change it, and owe nothing.
Last updated 2026-08-11.
The licence
The CLI, the component registry and every component you install are released under the MIT licence. That licence is the agreement; this page only describes it, and where the two disagree the licence text wins.
In practice MIT means you may use, copy, modify, merge, publish, distribute, sublicense and sell the code, including in closed-source and commercial products. The one condition is that the copyright notice and permission notice travel with substantial copies of the software.
What you own after installing
The files the CLI writes are yours. They are ordinary Kotlin in your repository, under your package, and nothing reaches back into them: there is no artifact to depend on, no runtime, and no update mechanism that could overwrite an edit you made.
You are not required to credit Lamintra in your app, keep any marker in the files, or tell anyone you used it.
No warranty
This is the part of MIT people skip, so it is worth stating in plain words: the software is provided without warranty of any kind, express or implied, and the authors are not liable for any claim, damages or other liability arising from it.
Concretely, nothing here promises the components are fit for your purpose, that a future Compose release will not break one, or that any component will continue to exist under the same name. What is promised is that a component you have already installed cannot change underneath you, because it is a file in your repository rather than a dependency.
The service, such as it is
There is no service. This is a static website and a jar you download. No account, no subscription, no paid tier, nothing to cancel and no uptime commitment. The registry is fetched from GitHub, so its availability is GitHub's.
There is also no acceptable use policy, because there is nothing to misuse: no upload, no submission and no user content of any kind.
Changes and contact
If these terms change the date at the top changes with them. The licence itself is versioned in the repository, so any change to it is visible in history rather than announced here.
Questions go to the issue tracker, which is a public channel and the only one.