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.

• ultra_faster_producer

  • No repository property

    Specify git repository URL in Cargo.toml to help users find more information, contribute, and for lib.rs to read more info.

  • Dependency futures 0.1 has issues

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

    futures crate

  • Dependency rdkafka 0.22.0 is significantly outdated

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

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

    rdkafka versions

  • Dependency rdkafka-sys =1.2.2 is significantly outdated

    Consider upgrading to 4.8.0+2.3.0 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.

    rdkafka-sys versions

  • Dependency tokio 0.1.21 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.37 to get all the fixes and improvements.

    clap versions

  • Latest stable release is old

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

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