ECZ-ID Shared Core (ecz-id)
The shared core of the ECZ-ID PyPI family. It provides:
- the public result contract (
ecz_id.result) that visibly separates local configuration/evidence posture from public Resolver evidence posture; - the stable reason-code register (
ecz_id.reason_codes); - safe bounded file enumeration (
ecz_id.fs) — never follows symlinks, never escapes the root, never executes discovered code; - redaction (
ecz_id.redaction) applied to every export; - URL validation and SSRF controls (
ecz_id.urlsafety) — https-only, no internal hosts, no private IPs; - offline mode (
ecz_id.offline); - report exporters (
ecz_id.report) — JSON, Markdown, text; - the contextual next-action selector (
ecz_id.next_actions) — routing only; - report exporters including SARIF (
ecz_id.report); - the machine-readable integration layer (
ecz_id.quiet_interface) — the packaged manifest, report envelope, footer and disclosure scan; - shared inspection assembly (
ecz_id.inspection), the shared specialist CLI (ecz_id.speccli), the Resolver client (ecz_id.resolver) and compare / share-guidance helpers (ecz_id.sharing); - Central Machine Interface manifest models (
ecz_id.machine_interface); - plugin discovery (
ecz_id.plugins) via theecz_id.pluginsentry-point group.
What this family never does
These packages inspect, explain and route only. They never issue or activate an ECZ-ID, never determine BOUND, never calculate carts or prices, never create proof, never execute discovered project, agent, MCP or robot code, never upload arbitrary source, and use no hidden telemetry.
No result is a safety, certification, approval, compliance, insurance or premium decision. Missing public proof is neutral — it does not mean unsafe. Local policy decides. Re-check before reliance.
CLI
ecz-id (owned exclusively by this distribution):
ecz-id about
ecz-id version
ecz-id plugins [--json]
ecz-id capabilities --json
ecz-id routes --json
ecz-id manifest --json # structured machine-readable manifest
ecz-id explain [ECZ-2001]
Machine-readable integration
Machine Interface · Manifest · Resolver · Operator setup · Developer guidance
Each installation includes structured machine-readable metadata for automation,
CI and supported integrations. The shared core provides the packaged manifest,
the report machine_interface envelope and the family-wide disclosure scan.
The core 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.
- 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
Need help choosing the right ECZ-ID route?
- Use ECZ-ID Trust Navigator if you are unsure what to buy or where to start.
- Use ECZ-ID Marketplace & Developer Tools if you arrived from VS Code, Open VSX, PyPI, GitHub, a package, an extension, or a developer tool.
- Use ECZ-ID Request Resolver Proof if you are reviewing another operator or vendor and need resolver-verifiable proof wording.
Start here: https://trustops.ecocitizenz.com/start#gpt-guidance
GPT guidance is public route guidance only. Official ECZ-ID state comes from TrustOps setup, Backend/Core truth and Resolver proof. 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.
Metadata
Release files for ecz-id 0.2.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 | |
|---|---|---|---|
| ecz_id-0.2.0.tar.gz | 57.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ecz_id-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 117.0 kB
Release files / ecz_id-0.2.0.tar.gz
| Download URL | ecz_id-0.2.0.tar.gz |
|---|---|
| Size | 57.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7ee6549813a0c4434a7be3cce4a163185cca1f1ec0e7d26cf0855f698f56db69
|
|
BLAKE2b-256 checksum How to use checksums |
52d008271a5c06de7ab1869d8cab42f6acef5ae11adad17e6c3c4e728acf68c3
|
| 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-0.2.0-py3-none-any.whl
| Download URL | ecz_id-0.2.0-py3-none-any.whl |
|---|---|
| Size | 59.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f94d54a475e6c5472a0c66e818878dcd106415498e8d8c3da4d0e4a38cfcd883
|
|
BLAKE2b-256 checksum How to use checksums |
71600526a4102ef2a4ac70b47a9f3b59ef1d4ab18f985ea234185bdec8aa5374
|
| 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