Lib.rs

Issues found

Based on crates you own that have been published to crates.io. The best way to monitor these issues is to subscribe to the atom feed in your RSS reader.

• zookeeper-zk

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["…"] to the Cargo.toml.

    Even if there are no categories that fit precisely, pick one that is least bad. You can also propose new categories in crates.io issue tracker.

    List of available categories

  • Dependency bytes 0.5 is significantly outdated

    Upgrade to 1.10.0 to get all the fixes, and avoid causing duplicate dependencies in projects.

    Easy way to bump dependencies: cargo install cargo-edit; cargo upgrade -i; Also check out Dependabot service on GitHub.

    bytes versions

  • Dependency mio 0.6 is significantly outdated

    Upgrade to 1.0.3 to get all the fixes, and avoid causing duplicate dependencies in projects.

    mio versions

  • Published crate doesn't match its repository

    Partially verified 35 files (includes 3 Cargo-generated).

    Files in the crates.io crate compared to the repository:

    • Cargo.lock not found.

    Fetched https://github.com/yangsenzk/rust-zookeeper.git 35929b80a3b728d97795b6e548a4f9126a4e947c.

    Checked on 2024-08-10

    This check is experimental.

    Forum thread

  • Imprecise dependency requirement rand = 0

    Cargo does not always pick latest versions of dependencies! Specify the version as rand = "0.9.1". If Cargo.lock ends up having an unexpectedly old version of the dependency, you might get a dependency that lacks features/APIs or important bugfixes that you depend on. This is most likely to happen when using the minimal-versions flag, used by users of old Rust versions.

    If you want to keep using truly minimal dependency requirements, please make sure you test them in CI with -Z minimal-versions Cargo option, because it's very easy to accidentally use a feature added in a later version.

    rand versions

If some of these crates are unmaintained and shouldn't be checked, yank them or add [badges.maintenance]
status = "deprecated" to their Cargo.toml.