Product guide
Repository and artifact lifecycle
Manage hosted, proxy, and group repository flows together with artifact discovery, storage, cleanup, access, and APIs.
Responsibility
Artifact Management owns the file, metadata, storage, and audit lifecycle after package publishing or upstream resolution.
Verified features
- Sixteen native formats, Raw generic storage, and limited Hugging Face compatibility
- Artifact search, browse, and paged inventory
- Proxy security, caching, cleanup, and retention
- Filesystem/S3 storage, transfer, access policy, and APIs
Repository lifecycle
A repository is created with organization, format, behavior type, and storage context. Hosted handles publishing, Proxy handles upstream resolution and caching, and Group handles ordered member resolution. Artifact records retain the same ownership context across search, browse, download, cleanup, and recovery by re-upload.
Control and evidence points
In production evaluation, verify identity and data-integrity evidence in addition to successful package downloads.
- Hosted publish and resolve results with the real package client
- Consistency of SHA-256, size, metadata, and storage-object relationships
- Upload or Download access-policy denial and anonymous-access boundary
- Reconciliation of audit, Package Usage, lifecycle, and operation records with the request
Explicit protocol boundaries
Interpret native support within the accepted client workflow for each format. Raw is path-addressed generic storage, and Hugging Face covers only the published compatibility subset. Unpublished behavior such as Terraform origin or module registry, Docker cross-repository mount optimization, and manifest garbage collection must not be assumed.