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.

• generic-ip

  • Dependency itertools ^0.12 is significantly outdated

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

    itertools versions

  • Optional dependency 'proptest' exposed as an implicit feature

    Cargo automatically makes publicly-available crate features for every optional dependency, unless the dependencies are referenced using dep: syntax. Feature 'proptest' may have been unintentional.

    Crate features

• bgpfu-netconf

  • Dependency russh ^0.39 is significantly outdated

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

    russh versions

  • Dependency russh-keys ^0.38 is significantly outdated

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

    russh-keys versions

  • Dependency tokio-rustls ^0.25 is significantly outdated

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

    tokio-rustls versions

  • Dependency quick-xml ^0.31 is outdated

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

    quick-xml versions

• rpsl

  • Dependency strum ^0.26 is outdated

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

    strum versions

  • Optional dependency 'proptest' exposed as an implicit feature

    Cargo automatically makes publicly-available crate features for every optional dependency, unless the dependencies are referenced using dep: syntax. Features 'proptest', 'regex', 'paste' may have been unintentional.

    Crate features

• rpsl, irrc, bgpfu-lib, bgpfu-netconf

  • Dependency thiserror ^1.0 is a bit outdated

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

    thiserror versions

• rfz

  • Dependency ansi_term 0.12 has issues

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

    ansi_term crate

  • Dependency directories 3.0 is significantly outdated

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

    directories versions

  • Dependency clap 2.33 is outdated

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

    clap versions

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

    If the crate is truly stable, why not make a 1.0.0 release?

    Maintenance status field docs

  • Missing categories

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

• irrc

  • Dependency nom ^7.0 is a bit outdated

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

    nom versions

  • Dependency strum ^0.26 is outdated

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

    strum versions

• juniper-jet

  • Dependency tonic ^0.9 is significantly outdated

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

    tonic versions

  • Latest prerelease is old

    It's been over 21 months. 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

  • Dependency prost ^0.11 is outdated

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

    prost versions

  • Dependency prost-build ^0.11 is outdated

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

    prost-build versions

  • Dependency tonic-build ^0.9 is outdated

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

    tonic-build versions

• bgpfu-cli

  • Dependency clap-verbosity-flag ^2.0 is outdated

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

    clap-verbosity-flag versions

• xmhell

  • Dependency quick-xml ^0.29 is significantly outdated

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

    quick-xml versions

No issues found in: prefixset

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