ECZ-ID Complete Trust Toolchain

The ECZ-ID Hub plus the complete sixteen-specialist estate in one install.

An ECZ-ID Extension Pack: one install adds the specialists below. The pack itself adds no scanner — each specialist runs locally and independently, and you can install components on their own instead.

Useful for

Useful across many legitimate roles. Commonly used by:

• Teams that want the entire ECZ-ID trust estate in one install
• Platform, security and enterprise architecture teams
• Operators routing across many trust surfaces

Relevant when you want the Hub and all sixteen specialists at once, you want the Hub to route to whichever specialist a workspace needs.

Included extensions

• ECZ-ID Hub (ecocitizenz.eczid) — the ECZ-ID trust cockpit — routes you to the right specialist.
• Agent Trust (ecocitizenz.eczid-ai-agents) — agent surfaces and resolver posture.
• MCP Trust (ecocitizenz.eczid-mcp-trust) — MCP server configuration and proof posture.
• API Security (ecocitizenz.eczid-api-security) — API surfaces and their proof posture.
• CI/CD Trust (ecocitizenz.eczid-cicd-trust) — pipeline and provenance artefacts.
• Dependency Security (ecocitizenz.eczid-dependency-security) — lockfile and SBOM evidence gaps.
• Compliance Risk (ecocitizenz.eczid-compliance-risk) — operational-resilience and audit artefacts.
• Vendor Risk (ecocitizenz.eczid-vendor-risk) — vendor / supplier counterparty surfaces.
• SBOM Readiness (ecocitizenz.eczid-sbom-readiness) — SBOM, lockfile and VEX evidence.
• DORA Readiness (ecocitizenz.eczid-dora-readiness) — operational-resilience and incident evidence.
• Cloud Trust (ecocitizenz.eczid-cloud-trust) — cloud / IaC surfaces and identity references.
• Counterparty Trust (ecocitizenz.eczid-counterparty-trust) — contract, due-diligence and counterparty evidence.
• Robotics Trust (ecocitizenz.eczid-robotics-trust) — robotics deployment descriptors and references.
• Humanoid Robot Insurance Readiness (ecocitizenz.eczid-humanoid-insurance) — humanoid deployment evidence for insurance review.
• Drone Insurance Readiness (ecocitizenz.eczid-drone-insurance) — drone / UAS evidence for insurance review.
• Robotaxi & Freight Insurance Readiness (ecocitizenz.eczid-robotaxi-freight-insurance) — autonomous fleet evidence for insurance review.
• Cargo & Marine Insurance Readiness (ecocitizenz.eczid-cargo-marine-insurance) — cargo / marine shipment evidence for insurance review.

Common workflows

• Install the Hub and all sixteen specialists at once.
• Let the Hub route you to whichever specialist a workspace needs.

Installation outcome

• Installs 17 ECZ-ID extensions (including the Hub) in one step.
• Every check stays free and local-first; nothing is uploaded and there is no telemetry.
• The Hub gives one cockpit; each specialist also works standalone.

Example result

ECZ-ID Complete Trust Toolchain  -  installs 17 extensions
- ECZ-ID Hub
- Agent Trust
- MCP Trust
- API Security
- CI/CD Trust
- Dependency Security
- Compliance Risk
- Vendor Risk
- SBOM Readiness
- DORA Readiness
- Cloud Trust
- Counterparty Trust
- Robotics Trust
- Humanoid Insurance Readiness
- Drone Insurance Readiness
- Robotaxi & Freight Insurance Readiness
- Cargo & Marine Insurance Readiness
Run: ECZ-ID: Show All Specialists

First-use path

1. Install the pack and trust your workspace.
2. Run ECZ-ID: Show All Specialists from the Hub to see what is installed.
3. Run a specialist's Review / Scan Workspace and review the evidence.

Privacy & permissions

Local-first. Filenames and paths only. No source / prompt / secret upload. No telemetry. Respects VS Code Workspace Trust. Each included extension makes no safety, approval, certification or compliance claim.

FAQ

Can I install the components separately? Yes — every extension in this pack is also available on its own.

Does the pack add any new scanning? No. A pack only groups extensions; all checks come from the specialists.

Free vs supported setup

• Free, local-first: local evidence review — no sign-in and no purchase to run a check.
• Supported setup (TrustOps): maintained ECZ-ID identity, public proof and lifecycle for the full ECZ-ID trust estate — relevant when you need a resolver-verifiable result others can check, not just local review.
• You never need to buy anything to get local value; supported setup is a separate, optional step handled entirely in TrustOps.

Python / CLI

Prefer Python, CI or terminal automation?

python -m pip install ecz-id
ecz-id --help

• Open the matching Python package: https://pypi.org/project/ecz-id/
• Explore all 10 ECZ-ID Python tools: https://developers.ecocitizenz.com/python

The Python tools run locally and inspect, explain and route only — the same role boundary as this extension. They do not issue an ECZ-ID, create public proof or replace Resolver proof.

Machine-readable facts

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.

Support & links

• Resolver (read-only proof): https://resolver.ecocitizenz.org
• TrustOps (supported setup): https://trustops.ecocitizenz.com/start
• Developer Gateway (docs): https://developers.ecocitizenz.com

ECZ-ID is independent trust infrastructure. Third-party names describe compatible ecosystems only and do not imply endorsement or affiliation. Local policy decides whether the evidence you review is sufficient.