Skip to main content

opencomplai-core

License: AGPL-3.0 PyPI Python

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 opencomplai meta-package (engine + CLI) or the opencomplai-cli command-line tool. Install opencomplai-core directly 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.7.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for opencomplai-core 0.7.1
File Size Uploaded
opencomplai_core-0.7.1.tar.gz 241.4 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for opencomplai-core 0.7.1
File Interpreter ABI Platform
opencomplai_core-0.7.1-py3-none-any.whl Python 3 none any Details

Total release size: 472.7 kB

Release files / opencomplai_core-0.7.1.tar.gz

Download URL opencomplai_core-0.7.1.tar.gz
Size 241.4 kB
Tags Source
SHA-256 checksum
How to use checksums
5284661b13c25a8ad3955c7eb90ebcc7a716d741631922b7464b8d5bd37bf7fd
BLAKE2b-256 checksum
How to use checksums
8f6a1cf2ce20abb6cff0769d6a2f912e8d89a4a110c393bc5d980a370b4142c2
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 Sep 23, 2026.

Transparency log

Release files / opencomplai_core-0.7.1-py3-none-any.whl

Download URL opencomplai_core-0.7.1-py3-none-any.whl
Size 231.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
eb7075f632ad951eea61a7eceb73848616d8421fc3d79f870e686d2ba644278c
BLAKE2b-256 checksum
How to use checksums
66d9b6d68fe70a17eceadc649dc465714cb50eaea9f7038743e73e5fe153ccc5
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 Sep 23, 2026.

Transparency log

Release history Release notifications | RSS feed

0.9.1

2 release files

0.9.0

2 release files

0.8.0

2 release files

This release

0.7.1 This release

2 release files

0.7.0

2 release files

0.6.0

2 release files

0.5.0

2 release files

0.4.0

2 release files

0.3.0

2 release files

0.1.2

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page