cargo-search

Search for packages

$ cargo search [query]

$ cargo search --limit [n] [query]

cargo search [OPTIONS] <QUERY>

<QUERY>
    The search term(s) or keywords to look for in crate names and descriptions on crates.io.

-q, --quiet
    Do not print cargo log messages, resulting in less verbose output.

--registry <REGISTRY>
    Name of the registry to use (defaults to 'crates-io'). Useful for custom registries.

--index <INDEX>
    URL of the registry index to use, overriding the default crates.io index.

--limit <LIMIT>
    Limit the number of results returned (defaults to a reasonable number, e.g., 10 or 20).

--color <WHEN>
    Control when colors are used in the output: auto (default), always, or never.

-h, --help
    Prints help information for the cargo search command and exits.

-v, --verbose
    Use verbose output, showing more details about operations.

-V, --version
    Print version information for cargo and exits.

--offline
    Run without accessing the network. For cargo search, this will cause the command to fail as it requires network access to query the registry.

cargo search is a powerful subcommand of the Rust package manager, cargo, designed to help developers discover and find Rust packages (known as crates) on the official Rust community's registry, crates.io. This command serves as the primary interface for exploring the vast ecosystem of open-source Rust libraries and executables.

When executed with a search <QUERY>, it efficiently queries the remote registry, filtering through thousands of available crates. It then returns a concise list of matching crates, typically displaying their names, a brief description of their functionality, and the latest published version. This facilitates the rapid identification of suitable dependencies for new or existing Rust projects, enabling developers to leverage the collective work of the Rust community and accelerate their development process. It's an indispensable tool for anyone building with Rust.

cargo search primarily relies on an active internet connection to query the remote crates.io registry. Running the command with --offline or without network access will result in an error or no results.
The search functionality typically matches against crate names and the short descriptions provided by crate authors, not against the full content of the crates or their documentation. Therefore, broad or highly specific queries might require refinement.
By default, cargo search limits the number of results displayed. To view more matches, the --limit option must be used with a higher value.

cargo search directly queries crates.io, which is the official and primary package registry for Rust. All public crates submitted by the community are indexed and made searchable through this platform, ensuring access to the vast majority of Rust's open-source ecosystem.

The search algorithm prioritizes matches in crate names and then considers keywords within the crate's description. It does not perform full-text searches of a crate's README, source code, or documentation. Users should be aware that the relevance of results is based on this limited metadata, and broader terms might yield more comprehensive results.

The cargo search subcommand has been a foundational element of the cargo toolchain since the early development phases of the Rust programming language. Its rapid integration was crucial for fostering a collaborative ecosystem, enabling developers to easily discover, evaluate, and integrate community-contributed code. While its core functionality of querying crates.io has remained consistent, minor enhancements have been implemented over time to improve search performance, refine output formatting, and introduce options like limiting results or specifying alternative registries.

cargo build(1), cargo install(1), cargo publish(1), cargo update(1), cargo add(1)