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.

• cloak

  • Dependency failure 0.1.1 has issues

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

    failure crate

  • Dependency ring 0.14.6 is significantly outdated

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

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

    ring versions

  • Dependency clap 2.32.0 is outdated

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

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

    clap versions

  • Dependency dirs 1.0.2 is outdated

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

    dirs versions

  • Dependency open 1.2.1 is outdated

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

    open versions

  • Dependency toml 0.5.0 is outdated

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

    toml 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

  • Using outdated edition for no reason

    We estimate that this crate requires at least Rust 1.31, which is newer than the last 2015-edition compiler. You can upgrade without breaking any compatibility. Run cargo fix --edition and update edition="…" in Cargo.toml.

    Using the latest edition helps avoid old quirks of the compiler, and ensures Rust code has consistent syntax and behavior across all projects.

    The Edition Guide

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