1. Overview
etchgit follows an open-core model. The protocol specification and core tools are open source. Enterprise features, hosted services, and brand assets are proprietary.
2. License Summary
| Component | License | Rationale |
|---|---|---|
| Protocol Specification | Apache 2.0 | Patent grant, open standard |
| Core Libraries (TS, Python, Go) | MIT | Maximum adoption |
| MCP Server | MIT | Zero-friction integration |
| Trust Badge | MIT | Embeddable verification |
| etch-id Specification | CC BY 4.0 | Open standard with attribution |
| Trust Badge Protocol | CC BY 4.0 | Open standard with attribution |
| Documentation | CC BY 4.0 | Attribution required |
| Brand Assets | Proprietary | Identity protection |
| Enterprise Features | Proprietary | Revenue protection |
3. License Rationale
MIT removes all friction for developers. Apache 2.0 provides patent protection for protocol implementers. CC BY 4.0 ensures attribution while enabling broad use.
4. Patent Policy
etchgit commits to not asserting patents against open source implementations of the etchgit protocol, etch-id headers, or Trust Badge protocol. Defensive use only. This pledge is irrevocable for open source implementations.
5. Contributing
Contributors must sign a CLA (one-time, covers all repos). The CLA grants etchgit rights to use contributions while contributors retain copyright. See GitHub for contribution guidelines.
See the full licensing documentation for complete details on license compatibility, third-party dependencies, and trademark policy.