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.

• fontfor

  • Dependency grid 0.13 is significantly outdated

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

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

    grid versions

  • Dependency ttf-parser 0.21 is significantly outdated

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

    ttf-parser versions

  • Dependency crossterm 0.27 is outdated

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

    crossterm versions

  • Dependency fontdb 0.16 is a bit outdated

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

    fontdb versions

  • Dependency ratatui 0.26 is significantly outdated

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

    ratatui versions

  • 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

  • Dependency tui-input 0.8.0 is outdated

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

    tui-input versions

• tui-markup

  • Dependency ansi_term 0.12 has issues

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

    ansi_term crate

  • Dependency ratatui 0.28 is significantly outdated

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

    ratatui versions

  • Dependency nom 7 is a bit outdated

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

    nom versions

  • Dependency nom_locate 4 is a bit outdated

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

    nom_locate versions

• amiya

  • Dependency async-channel 1 is outdated

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

    async-channel versions

  • Dependency async-io 1 is significantly outdated

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

    async-io versions

  • Dependency async-net 1 is outdated

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

    async-net versions

  • Dependency futures-lite 1 is outdated

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

    futures-lite versions

  • Imprecise dependency requirement async-channel = 1

    Cargo does not always pick latest versions of dependencies! Specify the version as async-channel = "2.3.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.

    async-channel 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

• bgpview-cli

  • 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 rustls 0.18 is significantly outdated

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

    rustls versions

  • Dependency webpki-roots 0.20 is significantly outdated

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

    webpki-roots versions

  • Imprecise dependency requirement anyhow = 1

    Cargo does not always pick latest versions of dependencies! Specify the version as anyhow = "1.0.97". 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.

    This crate does not bump semver-minor when adding new features, so to be safe you get all the features/APIs/fixes that your crate depends on, require a more specific patch version.

    anyhow versions

  • Dependency webpki 0.21 is outdated

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

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

    Maintenance status field docs

• gurgle

  • Dependency nanorand 0.6 is significantly outdated

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

    nanorand versions

  • Dependency thiserror 1 is a bit outdated

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

    thiserror versions

  • Imprecise dependency requirement once_cell = 1

    Cargo does not always pick latest versions of dependencies! Specify the version as once_cell = "1.21.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.

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

    Maintenance status field docs

• tui-markup-ansi-macro

  • Dependency ansi_term 0.12.1 has issues

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

    ansi_term crate

  • Dependency litrs 0.2.3 is significantly outdated

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

    litrs versions

  • Dependency tui-markup 0.2.1 is outdated

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

    tui-markup versions

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