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.

• dot-http

  • Latest stable release is old

    It's been over 5 years. How did the experiment go? 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

  • Dependency boa 0.5.1 has issues

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

    boa crate

  • Dependency reqwest 0.10.0-alpha.2 is significantly outdated

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

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

    reqwest versions

  • Dependency tokio 0.2 has issues

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

    tokio crate

  • Dependency clap 2.33.0 is outdated

    Consider upgrading to 4.5.27 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 gc 0.3.3 is outdated

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

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