ORAS
Radar: Initial
Apache-2.0
Pushes and pulls arbitrary artifacts through an OCI registry — Helm charts, SBOMs, signatures, models — using the registry as general artifact storage rather than image storage.
Container RegistryOCIArtifact StorageCloud NativeOCI Image, Runtime and Distribution
Specifications it implements
What this tool does to each specification, in the role vocabulary. Follow a standard through to standards.apievangelist.com for what it actually specifies.
| Standard | Role | What that means |
|---|---|---|
| OCI Image, Runtime and Distribution | transfers |
Pushes and pulls arbitrary artifacts through an OCI registry, not just images. |
Using this from an agent
- Interfaces
clilibrary- Install
-
brew
oras - Invoke
oras push <registry>/<repo>:<tag> <file>:<media-type>- Consumes
- filesystem
- Emits
- oci-image
- Runtime
- Needs network Deterministic Writes Needs credentials
Where it applies
Jobs this tool actually does, and the surface each one is exercised on.
Store a non-image artifact where the infrastructure already has auth, mirroring and retention.
coding-agentci-pipeline
The reason the Distribution spec matters beyond containers — registries turn out to be the artifact store organisations already run.
Attach an SBOM or attestation to an image as a referring artifact.
ci-pipeline
- Website
- https://oras.land
- Repository
- https://github.com/oras-project/oras
- License
- Apache-2.0 — reported by the GitHub API, verified 2026-09-17
- Stars
- 2433 · last commit 2026-09-15
- Also known as
- oras, OCI Registry As Storage
Reading this as an agent? Don't scrape the page — this entry is published as
structured data at
arrow_back
All tools by adoption
/tools.json,
against the tool.schema.json
schema, using the roles.json
vocabulary. Start at /llms.txt.