Supported Artifact Types
Supported Artifacts
Section titled “Supported Artifacts”Here is a list of the supported artifact types:
- Zarf Packages (Including UDS Packages)
- Docker Images
- OCI Images
- Helm Charts
- OpenTofu Modules
- OpenTofu Providers
- OCI Artifacts1
Recommended: Zarf Packages (Including UDS Packages). While UDS Registry can store multiple OCI artifact types, Zarf packages are the preferred, first-class unit of delivery. A Zarf package bundles the application’s container images, Helm charts, and manifests into a single deployable artifact, making it the most reliable way to move software across disconnected and mission environments.
UDS Packages build on Zarf (a Zarf package plus UDS-specific integration) and are the recommended format for delivering applications into UDS Core, preserving the metadata and structure needed for secure, repeatable deployments.
Supported Features
Section titled “Supported Features”UDS Registry supports publishing artifacts with standard OCI tooling. For every supported artifact type you can:
- Push from the CLI using OCI-compliant tools
- Pull with any OCI client
- Inspect the artifact in the UDS Registry UI (including tags, digests, and other metadata)
Some artifact types also support additional supply chain features, including SBOM and vulnerability scanning. Refer to the table below for details:
| Artifact Type | SBOM scan | Vulnerability scan |
|---|---|---|
| Zarf Packages | Supported | Supported |
| Docker Images | Coming soon | Coming soon |
| OCI Images | Coming soon | Coming soon |
Footnotes
Section titled “Footnotes”-
Any artifact packaged according to the Open Container Initiative (OCI) Image specification can be published to and pulled from UDS Registry using OCI-compliant tooling. Refer to Guidelines for Artifact Usage to learn more. ↩