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.

• ktra

  • Dependency bson 1.1 is significantly outdated

    Consider upgrading to 2.13.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.

    bson versions

  • Dependency mongodb 1.1 is significantly outdated

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

    mongodb versions

  • Dependency redis 0.19 is significantly outdated

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

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

    redis versions

  • Dependency semver 0.11 is significantly outdated

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

    semver versions

  • Dependency sha2 0.9 is significantly outdated

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

    sha2 versions

  • Dependency tokio-util 0.6 is significantly outdated

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

    tokio-util versions

  • Dependency tracing-subscriber 0.2 is significantly outdated

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

    tracing-subscriber versions

  • Dependency clap 2.33 is outdated

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

    clap versions

  • Dependency git2 0.13 is outdated

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

    git2 versions

  • Dependency openidconnect 2.1.1 is outdated

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

    openidconnect versions

  • Dependency rand 0.8 is a bit outdated

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

    rand versions

  • Dependency reqwest 0.11 is outdated

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

    reqwest versions

  • Dependency rust-argon2 0.8 is outdated

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

    rust-argon2 versions

  • Dependency thiserror 1.0 is a bit outdated

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

    thiserror versions

  • Dependency toml 0.5 is outdated

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

    toml versions

• sanjo

  • Dependency arrayvec 0.5.1 is significantly outdated

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

    arrayvec versions

  • Dependency failure 0.1.6 has issues

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

    failure crate

  • Dependency image 0.22.3 is significantly outdated

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

    image versions

  • Dependency imageproc 0.19.2 is significantly outdated

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

    imageproc versions

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

    clap versions

  • Dependency env_logger 0.7.1 is outdated

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

    env_logger versions

  • Dependency rusttype 0.8.2 is outdated

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

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

    Users pay attention to the latest release date. Even if the crate is perfectly fine as-is, users may not know that.

    Maintenance status field docs

• lamport_signature

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

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

    Maintenance status field docs

  • Dependency digest 0.7.2 is significantly outdated

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

    digest versions

  • Dependency rand 0.5.0 is significantly outdated

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

    rand versions

  • 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

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["cryptography"] 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

• plist-sys

  • 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

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

    More info

  • *-sys crate without links property

    If this crate uses C libraries with public symbols, consider adding links = "plist" to crate's Cargo.toml to avoid other libraries colliding with them. Note that the links property adds exclusivity to dependency resolution, but doesn't do any linking.

    This is also needed to protect your crate from duplicate older versions of itself. C symbols are global, and duplicate symbols can cause all sorts of breakage.

• buna

  • Dependency image 0.22.3 is significantly outdated

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

    image versions

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

    clap versions

  • Dependency env_logger 0.7.1 is outdated

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

    env_logger 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

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