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-client

  • Dependency compact_str ^0.4 is significantly outdated

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

    In Cargo, different 0.x versions are considered incompatible, so this is a semver-major upgrade.

    compact_str versions

  • Dependency hashbrown ^0.12.0 is significantly outdated

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

    hashbrown versions

  • Dependency num_enum ^0.5.6 is significantly outdated

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

    num_enum versions

  • Dependency strum ^0.23 is significantly outdated

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

    strum versions

  • Dependency hashlink ^0.8.0 is significantly outdated

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

    hashlink versions

  • Dependency md5 ^0.7.0 is outdated

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

    md5 versions

  • Dependency thiserror ^1.0.30 is outdated

    Upgrade to 2.0.18 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.

    thiserror versions

  • Imprecise dependency requirement rustls-pemfile = ^2

    Cargo does not always pick latest versions of dependencies! Specify the version as rustls-pemfile = "2.2.0". 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.

    rustls-pemfile versions

  • Optional dependency 'rsasl' exposed as an implicit feature

    Cargo automatically makes publicly-available crate features for every optional dependency, unless the dependencies are referenced using dep: syntax. Features 'rsasl', 'futures-rustls', 'hex', 'md5', 'rustls-webpki', 'linkme', 'rustls', 'rustls-pemfile' may have been unintentional.

    Crate features

• stuck

  • Dependency errno ^0.2.8 is significantly outdated

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

    errno versions

  • Dependency hashbrown ^0.12.0 is significantly outdated

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

    hashbrown versions

  • Dependency io-uring ^0.6.3 is significantly outdated

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

    io-uring versions

  • Dependency mio ^0.8.2 is significantly outdated

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

    mio versions

  • Dependency num_enum ^0.5.6 is significantly outdated

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

    num_enum versions

  • Dependency more-asserts ^0.2.2 is outdated

    Consider upgrading to 0.3.1 to get all the fixes and improvements.

    more-asserts versions

  • Dependency strum ^0.26 is outdated

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

    strum versions

• spawns

  • Published crate doesn't match its repository

    Verified 5 out of 6 files (includes 3 Cargo-generated).

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

    • Cargo.lock not found.
    • README.md exists, but elsewhere in the repo.

    Looked for the crate in spawns/. Fetched https://github.com/kezhuw/spawns.git tagged spawns_v0.2.6 (117c96f3c2d3a2862a598a5e3fa180b1d51d04d8).

    Checked on 2025-09-28

    This check is experimental.

    Forum thread

  • Missing keywords

    Help users find your crates. Add keywords = ["async", "runtime-agnostic", "task", "spawner", "thread"] (up to 5) to the Cargo.toml. Best keywords are alternative terms or their spellings that aren't in the name or description. Also add a keyword that precisely categorizes this crate and groups it with other similar crates.

  • Optional dependency 'spawns-executor' exposed as an implicit feature

    Cargo automatically makes publicly-available crate features for every optional dependency, unless the dependencies are referenced using dep: syntax. Features 'spawns-executor', 'spawns-compat' may have been unintentional.

    Crate features

• spawns-compat

  • Published crate doesn't match its repository

    Verified 8 out of 9 files (includes 3 Cargo-generated).

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

    • Cargo.lock not found.
    • README.md exists, but elsewhere in the repo.

    Looked for the crate in spawns-compat/. Fetched https://github.com/kezhuw/spawns.git tagged spawns-compat_v0.2.2 (95a619064664bba8d13a6cb7fc671740a0449c62).

    Checked on 2025-09-28

    Forum thread

  • Dependency async-global-executor ^2 is slightly outdated

    Consider upgrading to 3.1.0 to get all the fixes and improvements.

    async-global-executor versions

  • Imprecise dependency requirement async-global-executor = ^2

    Cargo does not always pick latest versions of dependencies! Specify the version as async-global-executor = "3.1.0". 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.

    async-global-executor versions

  • Missing keywords

    Help users find your crates. Add keywords = ["async", "task", "runtime-agnostic", "spawner", "thread"] (up to 5) to the Cargo.toml. Best keywords are alternative terms or their spellings that aren't in the name or description. Also add a keyword that precisely categorizes this crate and groups it with other similar crates.

  • Optional dependency 'linkme' exposed as an implicit feature

    Cargo automatically makes publicly-available crate features for every optional dependency, unless the dependencies are referenced using dep: syntax. Features 'linkme', 'spawns-core' may have been unintentional.

    Crate features

• spawns-executor

  • Published crate doesn't match its repository

    Verified 5 out of 6 files (includes 3 Cargo-generated).

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

    • Cargo.lock not found.
    • README.md exists, but elsewhere in the repo.

    Looked for the crate in spawns-executor/. Fetched https://github.com/kezhuw/spawns.git tagged spawns-executor_v0.1.2 (95a619064664bba8d13a6cb7fc671740a0449c62).

    Checked on 2025-09-28

    Forum thread

  • Missing keywords

    Help users find your crates. Add keywords = ["executor", "async", "task", "runtime-agnostic", "spawner"] (up to 5) to the Cargo.toml. Best keywords are alternative terms or their spellings that aren't in the name or description. Also add a keyword that precisely categorizes this crate and groups it with other similar crates.

• spawns-core

  • Published crate doesn't match its repository

    Verified 8 out of 9 files (includes 3 Cargo-generated).

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

    • Cargo.lock not found.
    • README.md exists, but elsewhere in the repo.

    Looked for the crate in spawns-core/. Fetched https://github.com/kezhuw/spawns.git tagged spawns-core_v1.1.2 (95a619064664bba8d13a6cb7fc671740a0449c62).

    Checked on 2025-09-28

    Forum thread

  • Missing keywords

    Help users find your crates. Add keywords = ["async", "runtime-agnostic", "task", "thread", "spawner"] (up to 5) to the Cargo.toml. Best keywords are alternative terms or their spellings that aren't in the name or description. Also add a keyword that precisely categorizes this crate and groups it with other similar crates.

  • Optional dependency 'linkme' exposed as an implicit feature

    Cargo automatically makes publicly-available crate features for every optional dependency, unless the dependencies are referenced using dep: syntax. Feature 'linkme' may have been unintentional.

    Crate features

• asyncs-sync

  • Published crate doesn't match its repository

    Verified 8 out of 9 files (includes 3 Cargo-generated).

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

    • Cargo.lock not found.
    • README.md exists, but elsewhere in the repo.

    Looked for the crate in asyncs-sync/. Fetched https://github.com/kezhuw/asyncs.git tagged v0.4.0 (a13627b038713e94cf8cd0e11bc3f2b501ccb321).

    Checked on 2025-07-13

    Forum thread

  • Missing keywords

    Help users find your crates. Add keywords = ["async", "asyncs", "runtime-agnostic", "facilities", "sync"] (up to 5) to the Cargo.toml. Best keywords are alternative terms or their spellings that aren't in the name or description. Also add a keyword that precisely categorizes this crate and groups it with other similar crates.

• spawns, spawns-compat, async-select, spawns-executor, asyncs-sync, spawns-core

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["asynchronous"] 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

• bookkeeper-client

  • Dependency compact_str ^0.7.1 is significantly outdated

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

    compact_str versions

  • Dependency prost ^0.11.9 is significantly outdated

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

    prost versions

  • Dependency sha-1 ^0.10.1 has issues

    It may not be actively developed any more. Consider changing the dependency.

    sha-1 crate

  • Dependency strum ^0.25 is significantly outdated

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

    strum versions

  • Dependency tonic ^0.9.2 is significantly outdated

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

    tonic versions

  • Dependency tonic-build ^0.9.2 is significantly outdated

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

    tonic-build versions

  • Dependency etcd-client ^0.11.1 is outdated

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

    etcd-client versions

  • Dependency hmac ^0.12.1 is a bit outdated

    Consider upgrading to 0.13.0 to get all the fixes and improvements.

    hmac versions

  • Dependency rand ^0.8.5 is outdated

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

    rand versions

  • Dependency zookeeper-client ^0.6.1 is outdated

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

    zookeeper-client versions

• asyncs

  • Missing keywords

    Help users find your crates. Add keywords = ["async", "runtime-agnostic", "facilities"] (up to 5) to the Cargo.toml. Best keywords are alternative terms or their spellings that aren't in the name or description. Also add a keyword that precisely categorizes this crate and groups it with other similar crates.

  • Optional dependency 'spawns' exposed as an implicit feature

    Cargo automatically makes publicly-available crate features for every optional dependency, unless the dependencies are referenced using dep: syntax. Features 'spawns', 'asyncs-test' may have been unintentional.

    Crate features

• async-select

  • Missing keywords

    Help users find your crates. Add keywords = ["async", "future", "multiplex", "tokio-runtime", "async-io"] (up to 5) to the Cargo.toml. Best keywords are alternative terms or their spellings that aren't in the name or description. Also add a keyword that precisely categorizes this crate and groups it with other similar crates.

• async-select-proc-macros

  • Imprecise dependency requirement syn = ^2

    Cargo does not always pick latest versions of dependencies! Specify the version as syn = "2.0.118". 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.

    This crate does not bump semver-minor when adding new features, so to be safe you get all the features/APIs/fixes that your crate depends on, require a more specific patch version.

    syn versions

  • No readme property

    Specify path to a README file for the project, so that information about is included in the crates.io tarball.

• stuck-macros

  • Could not fetch repository

    We've had trouble cloning git repo from https://github\.com/kezhuw/stuck\-macros\.git

    At the moment we only support git, and attempt fetching when we index a new release. Cloning is necessary for lib.rs to gather data that is missing on crates.io, e.g. to correctly resolve relative URLs in README files, which depend on repository layout and non-standard URL schemes of repository hosts.

  • Dependency syn ^1.0 is significantly outdated

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

    syn versions

  • README missing from crate tarball

    Cargo sometimes fails to package the README file. Ensure the path to the README in Cargo.toml is valid, and points to a file inside the crate's directory.

  • Latest stable release is old

    It's been over 4 years. Is this crate still maintained? Make a new release, either to refresh it, or to set

    [badges.maintenance]
    status = "deprecated"
    

    (or "as-is", "passively-maintained").

    If the crate is truly stable, why not make a 1.0.0 release?

    Maintenance status field docs

No issues found in: asyncs-test

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