ECZ-ID AI Provenance Inspection
Show what your model or dataset declares about itself — and route it to
ECZ-ID. ecz-id-ai-provenance inspects AI artefact provenance
declarations and model/dataset cards (YAML front matter) for ECZ-ID
configuration posture and declared lineage — locally, offline, in one
command. It inspects, explains and routes only.
It never issues or activates an ECZ-ID, never determines BOUND, never prices or carts, never certifies, and never executes discovered code. Missing public proof is neutral. Local policy decides. Re-check before reliance.
One-command free trial
$ uvx ecz-id-ai-provenance inspect ./my-model
# or: pipx run ecz-id-ai-provenance inspect ./my-model
Genuine example result
ECZ-ID inspection: ./my-model [ecz-id-ai-provenance]
A. configuration posture : PRESENT
B. public proof posture : NOT_CHECKED (neutral)
reason codes : ECZ-1000, ECZ-2002
Supported inputs
provenance_declaration.json,.ecz-provenance.jsonmodel_card.md/dataset_card.mdwith YAML front matter (needs the optionalyamlextra:pip install ecz-id-ai-provenance[yaml]; without it, cards degrade to a neutral note).- Observes declared lineage, dataset/model/repository/package/release/API/ agent relationships, base model, framework, licence, source, intended use and limitations.
Valuable free capabilities
Two-sided posture; scaffold a provenance declaration; compare drift;
JSON / Markdown / text / SARIF output; redaction; offline.
Unsupported inputs
Not a model evaluator, benchmark runner or dataset auditor. Does not fetch model weights or datasets.
What the result means / does not mean
Posture describes your local provenance declaration; the public side is neutral read-only Resolver evidence. Not a statement of authenticity, safety, fairness, accuracy, performance, lawful use or compliance.
Compare / drift
$ ecz-id-ai-provenance compare ./v1 ./v2 --json
CI use
$ ecz-id-ai-provenance inspect . --sarif > provenance.sarif
$ ecz-id-ai-provenance inspect . --json > provenance.json
Machine-readable integration
Machine Interface · Manifest · Resolver · Operator setup · Developer guidance
Each installation includes structured machine-readable metadata for automation,
CI and supported integrations. Every JSON report embeds a compact
machine_interface object with the canonical roots and safe, read-only actions.
The package runs locally to inspect, explain and route. It does not issue an ECZ-ID, write canonical truth, create public proof, price a cart, or replace Resolver proof.
$ ecz-id-ai-provenance manifest --json
- Central Machine Interface: https://machine.ecocitizenz.org/.well-known/ecz-machine.json
- Resolver (read-only public proof): https://resolver.ecocitizenz.org
- Operator setup (TrustOps): https://trustops.ecocitizenz.com/start
- Developer Gateway: https://developers.ecocitizenz.com
Privacy and no telemetry
Bounded, read-only, symlink-refusing inspection. No telemetry, no source
upload. Secrets redacted on every export. Offline mode
(--offline / ECZ_ID_OFFLINE=1) skips all network.
Need help choosing the right ECZ-ID route?
Use ECZ-ID GPT guidance: https://trustops.ecocitizenz.com/start#gpt-guidance
Route guidance only. TrustOps handles setup; Backend/Core writes truth; Resolver proves public state. Local policy decides reliance. Re-check before reliance.
Continue with ECZ-ID
- Operator setup: https://trustops.ecocitizenz.com/start
- Developer guidance: https://developers.ecocitizenz.com
- Public Resolver proof: https://resolver.ecocitizenz.org
- Central Machine Interface: https://machine.ecocitizenz.org/.well-known/ecz-machine.json
- EcoCitizenz: https://www.ecocitizenz.com
- Specifications and governance: https://www.ecocitizenz.org
- ECZ-ID on Visual Studio Marketplace: https://marketplace.visualstudio.com/publishers/ecocitizenz
- ECZ-ID on Open VSX: https://open-vsx.org/namespace/ecocitizenz
- Explore the ECZ-ID Python tool family: https://pypi.org/search/?q=ecz-id
Licence and trademarks
Apache-2.0 (see LICENSE, NOTICE). The code licence grants no trademark
rights; “ECZ-ID” and “EcoCitizenz” are trademarks of their owner(s) — see
TRADEMARKS.md. Changelog: CHANGELOG.md. Security: SECURITY.md.
CLI: ecz-id-ai-provenance | Import: ecz_id_ai_provenance | Plugin group: ecz_id.plugins
Metadata
Release files for ecz-id-ai-provenance 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 | |
|---|---|---|---|
| ecz_id_ai_provenance-0.1.2.tar.gz | 13.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ecz_id_ai_provenance-0.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 28.7 kB
Release files / ecz_id_ai_provenance-0.1.2.tar.gz
| Download URL | ecz_id_ai_provenance-0.1.2.tar.gz |
|---|---|
| Size | 13.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6e080d1fd225d090cfc81886de99a8c45053e09fe88f4008eb66d462143e758e
|
|
BLAKE2b-256 checksum How to use checksums |
ff783803e8c89f2ff8ec8a7d36331280ba1643d7149ea210e5d53bc98c673c93
|
| 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 13, 2026.
Transparency logRelease files / ecz_id_ai_provenance-0.1.2-py3-none-any.whl
| Download URL | ecz_id_ai_provenance-0.1.2-py3-none-any.whl |
|---|---|
| Size | 15.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
36bd96ff3c7b98f5f8565f3f129920c9fcbc1e46c6df7585ae4f1520f996c344
|
|
BLAKE2b-256 checksum How to use checksums |
fe9444499bfbb4869ff091632831665a1ce463f1b48fc6098a761fbfa964d0ad
|
| 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 13, 2026.
Transparency log