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.

• cshannon

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

    Nightly crates tend to have a short lifespan. We're delisting them if they're not updated frequently.

    Maintenance status field docs

  • Dependency owning_ref 0.4.1 has issues

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

    owning_ref crate

  • Dependency bit-vec 0.6.1 is a bit outdated

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

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

    bit-vec versions

  • Dependency clap 2.33.0 is outdated

    Upgrade to 4.5.21 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.1 is outdated

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

    env_logger versions

  • Dependency test_bin 0.3.0 is outdated

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

    test_bin 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.