Container Registry and Software Supply Chain Platform · View 06 of 33 · 2 · Structure
Contracts we own
- OCI distribution v2 plus the referrers API — standard, so any conformant client works
- Evidence API over gRPC with mTLS, five methods, read scoped by tenant
- The policy bundle is itself an OCI artifact, so bundle distribution reuses the registry rather than adding a service
Contracts we do not own
- Upstream registry rate limits and availability — mitigated by the proxy cache
- OSV and distro feed schemas — normalised on ingest into one advisory record
- A cached upstream image is treated as a first-party artifact and acquires its own evidence
Deliberately omitted
- Internal calls between platform services — see the container view
- The event topic list — see the evidence pipeline