opencomplai-core
The EU AI Act compliance risk engine at the heart of Opencomplai.
opencomplai-core turns a declared system-manifest.json and your source tree into a
deterministic, rule-based risk classification — no LLM calls, no network access, fully
reproducible.
It powers risk classification (UnacceptableRiskRule, AnnexIIIClassifierRule,
ProfilingDetectionRule, SubstantialModificationRule) and the code-corroboration scan
engine that cross-checks what a manifest claims against what the code actually does.
Install
pip install opencomplai-core
For PDF report generation, install the optional extra:
pip install "opencomplai-core[reports]"
Most users want the
opencomplaimeta-package (engine + CLI) or theopencomplai-clicommand-line tool. Installopencomplai-coredirectly when you are embedding the engine in your own application.
Quick start
Classify a model from a declared manifest
from opencomplai import assess, AssessmentInput, ModelMetadata
result = assess(AssessmentInput(
model=ModelMetadata(
name="loan-scorer",
version="1.0.0",
modality="tabular",
use_case="creditworthiness scoring for consumer loans",
deployment_context="production",
)
))
print(result.risk_level) # e.g. RiskLevel.HIGH
for rule in result.rule_results:
print(rule.rule_id, "PASS" if rule.passed else "FAIL")
Corroborate a manifest against the code
from pathlib import Path
from opencomplai_core.scan_engine import run_scan
report = run_scan(
repo_root=Path("."),
commit_ref="HEAD",
)
print(report.summary.result) # PASS / CONTROL_FAIL / ...
for finding in report.findings:
print(finding.finding_id, finding.mapped_taxonomy)
The scan engine extracts features from the repository, fuses evidence across detectors, and maps findings to EU AI Act taxonomy (Annex III high-risk areas, Article 5 prohibited practices, profiling under Article 6).
What you get
- Deterministic risk classification — same inputs always produce the same output, so results are auditable and CI-gateable.
- Code corroboration — detect when a manifest under-declares (claims minimal risk while the code does biometric identification, profiling, etc.).
- Merkle-linked evidence — findings carry verifiable evidence items for audit trails.
Documentation
Full docs, the EU AI Act concepts guide, and the SDK reference live at docs.opencomplai.com.
License
AGPL-3.0-only. See LICENSE.
Metadata
Release files for opencomplai-core 0.5.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| opencomplai_core-0.5.0.tar.gz | 187.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| opencomplai_core-0.5.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 374.3 kB
Release files / opencomplai_core-0.5.0.tar.gz
| Download URL | opencomplai_core-0.5.0.tar.gz |
|---|---|
| Size | 187.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2d3ce09e6a755a8000c98565346fe9409d09ef01111d99861022f185410566d2
|
|
BLAKE2b-256 checksum How to use checksums |
e5870f5a5d9a050a6006d243d09c8f28e75fd4de11a383fc4bf8b39be62d6afa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 26, 2026.
Transparency logRelease files / opencomplai_core-0.5.0-py3-none-any.whl
| Download URL | opencomplai_core-0.5.0-py3-none-any.whl |
|---|---|
| Size | 186.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c9f992fadefb33e5391aa3d470cdd33b39c9ac6b71b7f5367457cf5b362ff20f
|
|
BLAKE2b-256 checksum How to use checksums |
46d530eb2c2a1fced40a9948da562f3aa162c461fc58f73962b760c261d5e4ba
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 26, 2026.
Transparency log