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.

• prometheus-parse

  • 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

  • Imprecise dependency requirement once_cell = 1

    Cargo does not always pick latest versions of dependencies! Specify the version as once_cell = "1.20.0". If Cargo.lock ends up having an unexpectedly old version of the dependency, you might get a dependency that lacks features/APIs or important bugfixes that you depend on. This is most likely to happen when using the minimal-versions flag, used by users of old Rust versions.

    If you want to keep using truly minimal dependency requirements, please make sure you test them in CI with -Z minimal-versions Cargo option, because it's very easy to accidentally use a feature added in a later version.

    once_cell versions

  • Missing categories

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

• patroni-exporter

  • Dependency structopt ^0.3 has issues

    It has been losing active users, which may be a sign it's deprecated or obsolete. Consider replacing it with a different crate.

    structopt crate

  • Dependency hyper ^0.13 is significantly outdated

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

    hyper versions

  • Dependency prometheus ^0.9 is significantly outdated

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

    prometheus versions

  • Dependency sentry ^0.18 is significantly outdated

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

    sentry versions

  • Dependency tokio ^0.2.20 has issues

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

    tokio crate

  • Dependency tracing-subscriber ^0.2 is significantly outdated

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

    tracing-subscriber versions

  • Dependency uuid ^0.8 is significantly outdated

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

    uuid versions

  • Missing categories

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

    List of available categories

• bmp-protocol

  • Dependency bytes ^0.5 is significantly outdated

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

    bytes versions

  • Dependency hashbrown ^0.7 is significantly outdated

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

    hashbrown versions

  • Dependency tokio ^0.2 has issues

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

    tokio crate

  • Dependency tokio-util ^0.3 is significantly outdated

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

    tokio-util versions

  • Locked dependency version bgp-rs = 0.6

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    bgp-rs versions

• athenacli

  • Dependency rusoto_core ^0.45 has issues

    It has been losing active users, which may be a sign it's deprecated or obsolete. Consider replacing it with a different crate.

    rusoto_core crate

  • Dependency structopt ^0.3 has issues

    It has been losing active users, which may be a sign it's deprecated or obsolete. Consider replacing it with a different crate.

    structopt crate

  • Dependency hyper ^0.13 is significantly outdated

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

    hyper versions

  • Dependency hyper-proxy ^0.7 is significantly outdated

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

    hyper-proxy versions

  • Dependency rusoto_signature ^0.45 is significantly outdated

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

    rusoto_signature versions

  • Dependency tokio > 0.2.20 has issues

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

    tokio crate

  • Dependency tracing-subscriber ^0.2 is significantly outdated

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

    tracing-subscriber versions

  • Dependency uuid ^0.8 is significantly outdated

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

    uuid versions

  • Dependency ascii_table ^3.0 is outdated

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

    ascii_table versions

  • Dependency byte-unit ^4.0 is outdated

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

    byte-unit versions

  • Dependency http ^0.2 is outdated

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

    http versions

  • Dependency rusoto_athena ^0.45 is outdated

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

    rusoto_athena versions

  • Missing categories

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

    List of available categories

• bmp-client

  • Dependency tokio ^0.2 has issues

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

    tokio crate

  • Dependency tokio-util ^0.3 is significantly outdated

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

    tokio-util versions

  • Locked dependency version bmp-protocol = 0.1.3

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    bmp-protocol versions

• trk

  • Dependency structopt 0.2 has issues

    It has been losing active users, which may be a sign it's deprecated or obsolete. Consider replacing it with a different crate.

    structopt crate

  • Dependency read_input 0.5.2 is significantly outdated

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

    read_input versions

  • Dependency rusqlite 0.15 is significantly outdated

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

    rusqlite versions

  • Dependency drawille 0.2 is significantly outdated

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

    drawille 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

  • Dependency prettytable-rs ^0.8 is outdated

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

    prettytable-rs versions

  • Dependency termion 1 is outdated

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

    termion 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

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["visualization", "command-line-interface"] to the Cargo.toml.

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["data", "time-series", "plotter", "recorder", "terminal-based"] (up to 5) to the Cargo.toml. Best keywords are alternative terms or their spellings that aren't in the name or description. Also add a keyword that precisely categorizes this crate and groups it with other similar crates.

• inth-oauth2-azure

  • Dependency url 1.7 is significantly outdated

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

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

    Maintenance status field docs

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["open-id", "active-directory", "azure", "connect", "oauth2"] (up to 5) to the Cargo.toml. Best keywords are alternative terms or their spellings that aren't in the name or description. Also add a keyword that precisely categorizes this crate and groups it with other similar crates.

• bmp-protocol, bmp-client, athenacli, patroni-exporter

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

    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.