TürkçeDemo
Menu

Features and capabilities

Hosted, proxy, group, and package-format scope

Review repository-mode responsibilities, client-verified formats, and protocol boundaries.

Content statusVerified in sourceDocumentation versionLatest

Repository modes

  • Hosted: a managed repository where teams publish packages.
  • Proxy: upstream access, security controls, and caching.
  • Group: ordered resolution across multiple repositories.

Support level

Native means a real package-client acceptance test, generic storage means path-addressed storage, and limited compatibility means an explicitly bounded protocol subset.

Verified native formats

In the source snapshot, real-client acceptance coverage includes APT, Cargo, Conan, Conda, Docker or OCI, Git LFS, Go, Helm, Maven, npm, NuGet, PyPI, RubyGems, Swift, Terraform, and YUM or DNF.

  • Do not generalize Hosted, Proxy, and Group behavior under one acceptance assumption; test each repository type that will be used.
  • Record the actual base URL, authentication method, TLS trust, and minimum client version in client configuration.
  • Evidence publish, resolve, metadata, and failure behavior with an immutable test version and checksum.

Compatibility boundaries

Raw does not provide native package discovery and is published as path-addressed generic storage. Hugging Face support is a limited compatibility scope that excludes commit and upload, repository lifecycle, search, refs, Git or Xet, inference, and social APIs.

  • Do not assume unpublished Terraform origin or module-registry behavior.
  • Do not assume Docker cross-repository mount optimization or manifest garbage-collection support.
  • Revalidate the target client in the acceptance environment until the public per-format command and minimum-client matrix is complete.

Repository-type selection criteria

Use Hosted for team-produced packages, Proxy for controlled upstream access and caching, and Group to order multiple sources behind one client endpoint. Group does not create new artifact content itself; member order, access, and failure behavior must be accepted together.