licit Documentation
CLI tool for regulatory compliance and code traceability for AI-assisted development teams.
Table of Contents
| Document | Description |
|---|---|
| Quick Start | Guide to get licit up and running in 5 minutes |
| CLI Guide | Complete reference for all commands and options |
| Report Interpretation | How to read and act on compliance and gap analysis reports |
| FRIA Guide | Question-by-question guidance for completing the FRIA (Art. 27) |
| Auditor Guide | Compliance verification, evidence, preparation for regulatory audit |
| CI/CD Integration | GitHub Actions, GitLab CI, Jenkins — licit as a compliance gate |
| Configuration | Configuration guide for .licit.yaml with all fields |
| Compliance | Supported regulatory frameworks: EU AI Act and OWASP Agentic Top 10 |
| Architecture | System architecture, modules, phases, and design decisions |
| Data Models | Enums, dataclasses, and Pydantic schemas used internally |
| Provenance | Traceability system: heuristics, git analyzer, store, attestation |
| Changelog | Changelog system: watcher, differ, classifier, renderer |
| Security | Threat model, cryptographic signing, data protection |
| Best Practices | Recommendations for integrating licit into your workflow |
| Development | Contributor guide: setup, testing, linting, conventions |
| FAQ | Frequently asked questions and troubleshooting |
Quick Start
# Install
pip install licit-ai-cli
# Initialize in your project
cd your-project/
licit init
# View status
licit status
# Track code provenance
licit trace --stats
# Generate compliance report
licit reportCurrent Version
- v0.6.0 — Phases 1-6 completed (Foundation + Provenance + Changelog + EU AI Act + OWASP Agentic Top 10 + Reports)
- Python 3.12+ required
- 10 CLI commands, all functional
- 706 tests, mypy strict, ruff clean
License
MIT — see LICENSE in the project root.