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.

• cernan

  • Dependency base64 0.9.0 is significantly outdated

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

    base64 versions

  • Dependency chan-signal 0.3.1 has issues

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

    chan-signal crate

  • Dependency coco 0.3 has issues

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

    coco crate

  • Dependency futures 0.1 has issues

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

    futures crate

  • Dependency glob 0.2.11 is significantly outdated

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

    glob versions

  • Dependency mio 0.6.11 is significantly outdated

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

    mio versions

  • Dependency protobuf 1.7 is significantly outdated

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

    protobuf versions

  • Dependency rand 0.5 is significantly outdated

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

    rand versions

  • Dependency rdkafka 0.16 is significantly outdated

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

    rdkafka versions

  • Dependency reqwest 0.8 is significantly outdated

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

    reqwest versions

  • Dependency seahash 3.0 is significantly outdated

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

    seahash versions

  • Dependency tiny_http 0.6 is significantly outdated

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

    tiny_http versions

  • Dependency toml 0.4 is significantly outdated

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

    toml versions

  • Dependency url 1.6 is significantly outdated

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

    url versions

  • Dependency uuid 0.6 is significantly outdated

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

    uuid versions

  • Latest stable release is old

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

  • Dependency clap 2.27 is outdated

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

    clap versions

  • Dependency fern 0.5 is outdated

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

    fern versions

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["development-tools::debugging"] to the Cargo.toml.

    Even if there are no categories that fit precisely, pick one that is least bad. You can also propose new categories in crates.io issue tracker.

    List of available categories

• quantiles

  • Latest stable release is old

    It's been over 7 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").

    Maintenance status field docs

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["algorithms"] to the Cargo.toml.

    List of available categories

• quantiles, cernan, hopper

  • The Cargo package has no git commit information

    Before publishing a package, make sure all packaged files are committed to the repository, and there are no "dirty" files. Push this commit to crate's public repository.

    To protect against supply chain attacks similar to CVE-2024-3094, lib.rs will soon start flagging non-reproducible packages without public source code as suspicious. Currently only git repositories are supported (but may be hosted anywhere, not just GitHub). If you'd like a different SCM supported, please file a feature request.

    More info

• hopper

  • Latest stable release is old

    It's been over 7 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").

    Maintenance status field docs

  • Dependency bincode 1.0 is slightly outdated

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

    bincode versions

  • Using outdated edition for no reason

    We estimate that this crate requires at least Rust 1.37, 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.