License Compliance Checkerv1.0.0
Scans AI models, software packages, and agentic pipelines for license compliance across 8 ecosystems. Detects HuggingFace model references in code, GGUF/ONNX files, and generates EU AI Act Article 53 audit evidence with an honest dataset risk registry.
Install in 60 seconds
bashpip install license-compliance-checkerApache 2.0 · zero telemetry · source Regulation (EU) 2024/1689 (Article 53).
Why License Compliance Checker exists
Obligations for providers of general-purpose AI models
Article 53 has been applicable since 2 August 2025 (Art. 113(b)). GPAI providers placing models on the EU market today owe four things. Technical documentation (53(1)(a)). Downstream-provider information packs (53(1)(b), Annex XII). A copyright-compliance policy aligned with Directive (EU) 2019/790 Article 4(3) (53(1)(c)), plus a public training-data summary on the AI Office template (53(1)(d)). Commission-imposed fines under Article 101 are excluded from the 2025-08-02 date by Art. 113(b); they become exercisable on 2 August 2026, at up to €15M or 3% of global annual turnover, whichever is higher. Transitional regime per Art. 111(3): GPAI models placed on the EU market before 2 August 2025 have until 2 August 2027 to comply. The operational reality is simpler to state than to meet. The copyright-policy and training-data-summary obligations require auditable evidence at the dataset level, not assertions in a model card.
When the findings land on a governance desk
Tools surface problems. Programmes solve them.
License Compliance Checker hands you the file. The work that follows (programme design, board narrative, regulator engagement) is what AskAjay.ai (the advisory arm of AI Exponent LLC) does.
Explore advisory at AskAjay.ai →Other AiExponent flagship tools