eval-conformance-suite
Run executable rubric-spec adapter checks before claiming schema compatibility.
eval-conformance-suite is for adapter maintainers and evaluation-platform integrators. Its differentiator is an executable, framework-neutral contract: it imports a target Python adapter module and runs 18 synthetic cases covering scale types, anchors, weights, tie-break rules, judge prompt contracts, provenance, validation errors, lint findings, deterministic serialization, and round-trip field preservation.
Inspectable Output
runwrites a JSON report with the target module, overall pass state, and every case name, boolean result, and detail string.badgewrites SVG text to stdout for a caller-supplied label.
The badge command does not run conformance or read a report; it currently renders a passing badge unconditionally. Generate and publish a badge only after independently confirming that the run JSON passed.
Runtime Boundary
Checks run in the local Python process and make no built-in network requests or model calls. The --against value is imported with importlib, and the suite calls that module's to_spec and from_spec functions. Running against an untrusted adapter executes untrusted Python code.
Install
python -m pip install eval-conformance-suite==0.1.2
rubric-spec>=0.1.1 is installed as a dependency. For development from a clone:
python -m pip install -e .
Quickstart
eval-conformance-suite run \
--against rubric_spec.adapters.inspect_ai \
> conformance.json
eval-conformance-suite badge \
--against rubric_spec.adapters.inspect_ai \
> rubric-spec-conformance.svg
The bundled CI also exercises the PromptFoo, DeepEval, LangSmith, and EvalKit adapters shipped by rubric-spec.
See docs/architecture.md and the synthetic report template in examples/conformance_report_template.md.
Release Status
Registry status verified July 13, 2026: version 0.1.2 is published on PyPI and tagged v0.1.2 in the public repository. The project is alpha software. No framework certification, partnership, or adoption claim is made.
Limits
Passing means the adapter satisfied this package's synthetic rubric-spec cases. It is not a framework benchmark, security audit, production-runtime test, or independent certification.
Next Action
Run the suite against the trusted adapter module you intend to support, inspect all 18 case details, fix every failure, and publish a badge only after the JSON report passes.
Metadata
Release files for eval-conformance-suite 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| eval_conformance_suite-0.1.2.tar.gz | 8.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| eval_conformance_suite-0.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 18.2 kB
Release files / eval_conformance_suite-0.1.2.tar.gz
| Download URL | eval_conformance_suite-0.1.2.tar.gz |
|---|---|
| Size | 8.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a8c9e027f11098a72eb2b8fe20fb0d03ea83ed9c2076e56457c2449ecbf5c37c
|
|
BLAKE2b-256 checksum How to use checksums |
232e017f434adc180cdd02515059b07c96ce708feef186b35c3820391d380c43
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 13, 2026.
Transparency logRelease files / eval_conformance_suite-0.1.2-py3-none-any.whl
| Download URL | eval_conformance_suite-0.1.2-py3-none-any.whl |
|---|---|
| Size | 9.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
989a154c8cde792fddca0950cc13b775d5b62671c6d39c6555a1a3412fa5d855
|
|
BLAKE2b-256 checksum How to use checksums |
332eb611120f648da90596a7a4a1d4064cc85db1d7e36282347628172d6c62b4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 13, 2026.
Transparency log