Licensing · v0.10.2
Permissive package licensing with explicit boundaries
RuleOak keeps package-local license metadata, SPDX headers, full license texts, and REUSE checks so developers and scanners can identify the license that applies to each public component.
| Component | License | Notes |
|---|---|---|
packages/protocol/ | MIT | Contracts, JSON Schemas, validators, fixtures, and TypeScript types. |
packages/core/ | Apache-2.0 | Authorization runtime and integration primitives. |
packages/cli/ | Apache-2.0 | CLI, gateways, local service, policy, approval, learning, and audit workflows. |
| Repository docs/tests/examples/scripts/CI | Apache-2.0 unless stated otherwise | See file-level SPDX and repository licensing files. |
Compliance files
Use LICENSE.md, package-local LICENSE metadata, NOTICE.md, TRADEMARK.md, REUSE.toml, SPDX headers, and the complete license texts under LICENSES/.
Trademark is separate from the code licenses
The RuleOak™ name and logo are not granted by the MIT or Apache-2.0 code licenses. See TRADEMARK.md for the repository’s current trademark terms.