rai-check-core
Shared audit findings, evidence manifests, history, and reporting APIs.
Configured runs can include standards-coverage in audit.report_formats to
write a standalone JSON evidence-coverage artifact. History exports are available
from the CLI:
rai-check export standards-coverage audit-run.json
rai-check export history-dashboard --directory .rai-check/history
rai-check export eu-post-market --directory .rai-check/history
Standards coverage and EU AI Act-oriented post-market reports summarize recorded evidence. They do not make a compliance claim.
Configs, audit reports, evidence manifests, agent traces, and LLM suites use
versioned JSON Schemas. Existing unversioned inputs are migrated to schema version
1.0 during loading.
1 maintainer
Metadata
1 maintainer
Release files for rai-check-core 0.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| rai_check_core-0.0.1.tar.gz | 36.2 kB | With provenance | Details for rai_check_core-0.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| rai_check_core-0.0.1-py3-none-any.whl | Python 3 | none | any | Details for rai_check_core-0.0.1-py3-none-any.whl |
Total release size: 75.0 kB
Release files / rai_check_core-0.0.1.tar.gz
| Download URL | rai_check_core-0.0.1.tar.gz |
|---|---|
| Size | 36.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
89b59d0202fae7d989d679281281cb67e2ca97f2653d5c4277e21017c8a3f2a8
|
|
BLAKE2b-256 checksum How to use checksums |
2e3c5c030e63450539e99b9a6d1d58c4e96e9462b73ae2597c01217f98b1d124
|
| 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 21, 2026.
Transparency logRelease files / rai_check_core-0.0.1-py3-none-any.whl
| Download URL | rai_check_core-0.0.1-py3-none-any.whl |
|---|---|
| Size | 38.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
465a4a853a47897e5d86ecb5d5f566e47a43075788bfb8434ef0cb8ea2ed0ea7
|
|
BLAKE2b-256 checksum How to use checksums |
2ab71ff7588f4b2f873dbaebfa8382c4e45871225c96c1a83b50ba71239a010c
|
| 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 21, 2026.
Transparency logSecurity for rai-check-core 0.0.1
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for rai_check_core-0.0.1.tar.gz
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 21, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
