Cargo Sparse Registry

Generally, Rust applications use the "Git dependencies" approach to reference dependencies. When a Rust package specifies a Git dependency in its Cargo.toml file, Cargo clones the Git repository and determines the exact version of the required dependency. To address the downsides of such an approach (e.g., increased complexity in managing dependencies, increased storage requirements, and so on), Rust introduced a new experimental feature called sparse registries. In this approach, a separate registry provides package metadata via JSON HTTP API instead of Git.

Space Packages provide support for sparse registries letting you store and share Rust packages:

• Create a Cargo Registry

• Publish Rust Packages

• Get Rust Packages