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.

• rmqfwd

  • Dependency structopt 0.2 has issues

    It has been losing active users, which may be a sign it's deprecated or obsolete. Consider replacing it with a different crate.

    structopt crate

  • Dependency env_logger 0.6 is significantly outdated

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

    env_logger versions

  • Dependency failure 0.1 has issues

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

    failure crate

  • Dependency failure_derive 0.1 has issues

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

    failure_derive crate

  • Dependency futures 0.1 has issues

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

    futures crate

  • Dependency hyper 0.12 is significantly outdated

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

    hyper versions

  • Dependency lapin-futures ^0.15 is significantly outdated

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

    lapin-futures versions

  • Dependency tokio 0.1 has issues

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

    tokio crate

  • Dependency tokio-codec 0.1 has issues

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

    tokio-codec crate

  • Dependency tokio-fs 0.1 has issues

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

    tokio-fs crate

  • Dependency try_from is not needed

    try_from is in the standard library

    try_from crate

  • Dependency url 1.7 is significantly outdated

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

    url versions

  • Dependency clap 2 is outdated

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

    clap versions

  • Dependency toml 0.5 is outdated

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

    toml versions

  • Imprecise dependency requirement clap = 2

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

    clap versions

  • Latest stable release is old

    It's been over 5 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

  • License MIT/Apache-2.0 is not in SPDX syntax

    Use OR instead of /.

    SPDX license list

  • Missing categories

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

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