AI System Compliance and Open Source Management
Beyond managing code generated by AI coding tools, the AI system itself also requires open source management. AI frameworks, pre-trained models, and training datasets all make extensive use of open source and open data.
If your organization already operates ISO/IEC 5230 (license compliance) and ISO/IEC 18974 (security assurance), the same principles should be applied in AI system development stages.
Three areas where open source is used
AI system
├── 1. AI frameworks and libraries
│ (PyTorch, TensorFlow, Hugging Face Transformers, LangChain etc.)
│ → Apply existing ISO 5230 process as-is
│
├── 2. Pre-trained models
│ (Llama, Mistral, Falcon, BERT etc.)
│ → Custom licenses must be checked per model
│
└── 3. Training datasets
(Common Crawl, Wikipedia, CC-BY datasets etc.)
→ Fulfill open-data license obligations
1. AI Frameworks and Libraries
Apply the ISO/IEC 5230 process just as you do for normal software dependencies. Scan AI code repositories with existing SBOM generation tools (such as syft, cdxgen, and FOSSLight).
| Framework | License | Commercial Use | Key Obligations |
|---|---|---|---|
| PyTorch | BSD 3-Clause | ✅ | Copyright notice |
| TensorFlow | Apache 2.0 | ✅ | Copyright notice, modification notice |
| Hugging Face Transformers | Apache 2.0 | ✅ | Copyright notice |
| LangChain | MIT | ✅ | Copyright notice |
| scikit-learn | BSD 3-Clause | ✅ | Copyright notice |
2. Pre-trained Models
Unlike common open source libraries, pre-trained models often use custom licenses. Be careful, because they may include commercial-use restrictions, MAU-based conditions, and derivative model disclosure obligations.
| License Type | Representative Models | Commercial Use | Derivative Model Disclosure |
|---|---|---|---|
| Apache 2.0 | Falcon, Mistral 7B | ✅ | ❌ |
| MIT | GPT-2, GPT-J | ✅ | ❌ |
| Llama Community License | Llama 3 | Conditional (MAU under 700M) | ❌ |
| CC-BY 4.0 | Some academic models | ✅ | Attribution required |
| CC-BY-NC | Some research models | ❌ Non-commercial only | — |
AI model licenses are not standardized. Always verify the model card and license directly in places like the Hugging Face model hub.
- Whether commercial use is allowed
- MAU- or revenue-based restriction conditions
- Fine-tuned derivative model disclosure requirements
- Model disclosure requirements for AI systems
Include model information in AI SBOM
Build an AI SBOM that includes pre-trained models in the SBOM. Example based on SPDX 3.0 AI Profile:
- name: 'meta-llama/Llama-3.1-8B'
version: '3.1'
license: 'Llama Community License Agreement'
primaryPurpose: 'inference'
modelCard: 'https://huggingface.co/meta-llama/Llama-3.1-8B'
Existing SBOM tools do not automatically detect model files, so model and dataset entries should be added manually.
3. Training Datasets
If open data licenses apply to datasets used for AI model training, corresponding obligations must be fulfilled.
| License | Attribution | Commercial Use | Share-Alike Required |
|---|---|---|---|
| CC0 | ❌ | ✅ | ❌ |
| CC-BY 4.0 | ✅ | ✅ | ❌ |
| CC-BY-SA 4.0 | ✅ | ✅ | ✅ |
| CC-BY-NC 4.0 | ✅ | ❌ Non-commercial only | ❌ |
- CC-BY family: Specify dataset sources in the model card or system documentation.
- CC-BY-SA: Coordinate derivative model licensing treatment with legal in advance.
ISO/IEC 42001 and the role of open source owners
When an organization prepares an ISO/IEC 42001 AI management system, the clauses below directly connect to open source management.
| ISO 42001 Clause | Open Source Owner Role |
|---|---|
| §5.2 AI Policy | Include open source usage principles in AI policy |
| §6.1.2 AI Risk Assessment | Identify and assess OSS license and vulnerability risks |
| §7.5 Documentation | Establish and maintain AI SBOM |
| §8.5 AI Lifecycle | Review OSS compliance by development stage |
| §8.6 AI Data | Manage dataset licenses |
| §8.8 External AI Procurement | Verify external open source model supply chains |
ISO/IEC 42001 certification covers overall AI system governance and is conducted separately from ISO 5230/18974 conformance. Organizations that already established ISO 5230/18974 systems can reuse the cross-mapped items above to streamline ISO 42001 preparation.
Learn More
- OpenChain KWG — AI Compliance Guide: 7. AI Compliance
- OpenChain KWG — ISO/IEC 42001 Guide: Practical ISO 42001 guidance for open source owners
- SPDX 3.0 AI Profile: Official SPDX documentation