opencontainers/image-spec
OCI Image Format
Build with Backblaze B2
SDKs, agent skills, IDE extensions, and reference pipelines from Backblaze Labs. All open source.
Loading star history...
Where it stands
Rank, growth pace and release cadence relative to everything GStars tracks.
No releases in the last 90 days; the most recent was 612 days ago, with 83 contributors on GitHub.
Peaked at #60 in the weekly ranking the week of Nov 30, its best in the past year.
Use Cases & Benefits
- Defines and maintains the OCI Image Format specification for container images including Go types and validation tooling.
- Provides a stable, open, and extensible container image format compatible across different container runtimes and tools.
- Use for creating and validating container images that conform to a standardized open specification.
- Use for implementing container runtimes that need to unpack and run OCI-compliant filesystem bundles.
- Use for developing container registries or distribution tools that push and pull OCI images using standardized APIs.
Should you depend on it?
License terms, project hygiene and risks, from GitHub metadata and GStars' snapshots.
License
Apache 2.0
Permissive: commercial use, modification and redistribution are allowed with attribution; includes an explicit patent grant from contributors.
Community files
- README: present
- Code of conduct: present
Watch-outs
No watch-outs from GStars' checks.
General guidance from repository metadata, not legal advice. How we score
From the README
The OCI Image Format project creates and maintains the software shipping container image format spec (OCI Image Format).
This repository also provides Go types, intra-blob validation tooling, and JSON Schema. The Go types and validation should be compatible with the current Go release; earlier Go releases are not supported.
The OCI Image Format partner project is the OCI Runtime Spec project. The Runtime Specification outlines how to run a "filesystem bundle" that is unpacked on disk. At a high-level an OCI implementation would download an OCI Image then unpack that image into an OCI Runtime filesystem bundle. At this point the OCI Runtime Bundle would be run by an OCI Runtime.
This entire workflow supports the UX that users have come to expect from container engines like Docker and rkt: primarily, the ability to run an image with no additional arguments:
To support this UX the OCI Image Format contains sufficient information to launch the application on the target platform (e.g. command, arguments, environment variables, etc).
The OCI Distribution Spec Project defines an API protocol to facilitate and standardize the distribution of content. This API includes support for pushing and pulling OCI images to an OCI conformant registry.
Daily snapshots
Stars gained per day, and how forks and open issues moved, from GStars' daily snapshots
Forks
908+30
Open issues
77+4
Compared with peers in DevOps
Fastest-growing repositories GStars tracks in this cohort for the week of Nov 1, by 7-day star growth
| Repository | Stars | +7d | Health | Last release |
|---|---|---|---|---|
| milind-soni/OpenMausBot | 13.5K | +6.0K | 45 | today |
| DuarteSantos8/openGym | 19.7K | +2.4K | 60 | 2 days ago |
| AstrBotDevs/AstrBot | 46.2K | +1.4K | 65 | 5 days ago |
| elie222/rakazo | 7.2K | +922 | 59 | 26 days ago |
| superplanehq/superplane | 8.8K | +435 | 60 | 7 days ago |
| opencontainers/image-spec | 4.5K | — | 40 | 612 days ago |
| Category median | 13.5K | +1.4K | 60 | — |
Also by opencontainers
Other repositories from this maintainer that GStars tracks
Discover Repositories
Search across tracked repositories by name or description