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.

• ed_join

  • Dependency crossbeam-channel 0.3.9 is significantly outdated

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

    crossbeam-channel versions

  • Dependency dialoguer 0.4.0 is significantly outdated

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

    dialoguer versions

  • Dependency error-chain 0.12.1 has issues

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

    error-chain crate

  • Dependency indicatif 0.12.0 is significantly outdated

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

    indicatif versions

  • Dependency clap 2.33.0 is outdated

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

    clap versions

  • Dependency env_logger 0.7.0 is outdated

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

    env_logger 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").

    Users pay attention to the latest release date. Even if the crate is perfectly fine as-is, users may not know that.

    Maintenance status field docs

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