Works alongside
What an ECZ-ID SDK Passport sits beside
An SDK Passport complements package registries and the repositories behind them. The registry distributes your library; the Passport publishes who stands behind it.
Adjacent systems
What each already does, and what the Passport adds
ECZ-ID complements your frameworks, protocols, OAuth, cloud IAM and workload identity. It replaces none of them and stays outside the execution path.
Package registries — npm, PyPI, Maven, NuGet and others
- What it does
- Distribute the versions of your library.
- What an ECZ-ID adds
- One publisher-linked identity for the library across every registry it is published to.
Source repositories
- What it does
- Host the code a library, plugin or server is built from.
- What an ECZ-ID adds
- A binding from the repository to the enduring subject, recorded with where it was learned.
Adjacent identities
The Passports that surround this one
Each is a separate subject with its own operator and its own identity. None is issued for you, and none is implied by holding this one.
ECZ-ID API Passport™
Most SDKs wrap an API. The API keeps its own identity, whichever SDKs call it.
ECZ-ID Plugin Passport™
SDKs are the building blocks of plugins, and each plugin is identified in its own right.
ECZ-ID Service & Workload Passport™
Libraries run inside services and workloads, which are separate enduring subjects.