---
title: "Licences"
description: "MIT for the app, CC0 for the catalogue data, and what that means for the LGPL wasm kernel underneath."
url: https://kaicad.barpom.xyz/docs/reference/licences
schema: "0.1"
---

# Licences

| Part | Licence |
| --- | --- |
| Application code | **MIT** |
| Catalogue data — materials, fixtures, standards | **CC0-1.0** |
| `replicad-opencascadejs` (the CAD kernel, as wasm) | LGPL-2.1, loaded unmodified |

## Why the catalogue is CC0

The catalogue is deliberately the most permissive thing here, and that is a decision rather
than an oversight.

A fixture entry in this format is not a solid. It is a solid, **plus a machining recipe for
the parts it joins, plus the dimensions it determines, plus the design rules the validator
then enforces**. That combination does not exist anywhere open, and its value is as a
*standard* rather than as an asset. The more tools that adopt the format, the better it gets.
CC0 removes even attribution friction.

## The discipline behind the data

- Encode **published standard dimensions**. Cite the standard on the page.
- **Never redistribute vendor CAD files.** Reference part numbers instead.

Every generated catalogue page names its source file and its licence in the footer, because
saying so on the page is half the point of publishing it.

## The kernel

The OCCT kernel is loaded as an unmodified WebAssembly module — the dynamic-linking case
under LGPL-2.1 — which imposes no obligation beyond leaving it replaceable. It is not
statically linked into the app, and it is not modified.