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.

• barkdocs

  • Dependency pulldown-cmark 0.12 is significantly outdated

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

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

    pulldown-cmark versions

  • Imprecise dependency requirement anyhow = 1

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

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

    crossterm versions

  • Dependency ratatui 0.29 is outdated

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

    ratatui versions

  • Dependency reqwest 0.12 is outdated

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

    reqwest versions

  • Dependency toml 0.8 is outdated

    Consider upgrading to 1.1.0+spec-1.1.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.

    toml versions

• ttl

  • Dependency is-terminal is not needed

    IsTerminal trait is in the standard library

    is-terminal crate

  • Imprecise dependency requirement anyhow = 1

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

    anyhow versions

• jsonfizz

  • Dependency dirs 4.0 is significantly outdated

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

    dirs versions

  • Dependency owo-colors 3.2.0 is significantly outdated

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

    owo-colors versions

  • Dependency serde_yaml 0.8 has issues

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

    serde_yaml crate

  • Dependency indicatif 0.17 is outdated

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

    indicatif versions

  • Dependency jsonschema 0.17 is outdated

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

    jsonschema versions

  • Dependency notify 6.1 is outdated

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

    notify versions

  • Dependency thiserror 1.0.40 is outdated

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

    thiserror versions

  • Dependency toml 0.5.9 is outdated

    Upgrade to 1.1.0+spec-1.1.0 to get all the fixes, and avoid causing duplicate dependencies in projects.

    toml versions

• barklog

  • Imprecise dependency requirement anyhow = 1

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

    anyhow versions

  • Dependency ansi-to-tui 7 is outdated

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

    ansi-to-tui versions

  • Dependency crossterm 0.28 is outdated

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

    crossterm versions

  • Dependency ratatui 0.29 is outdated

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

    ratatui versions

  • Dependency toml 0.8 is outdated

    Consider upgrading to 1.1.0+spec-1.1.0 to get all the fixes and improvements.

    toml versions

• xfr

  • Imprecise dependency requirement anyhow = 1

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

    anyhow versions

  • Dependency reqwest 0.12 is outdated

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

    reqwest versions

• kaioken

  • Dependency tokio-tungstenite 0.26 is significantly outdated

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

    tokio-tungstenite versions

  • Dependency clap_mangen 0.2 is a bit outdated

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

    clap_mangen versions

  • Dependency crossterm 0.28 is outdated

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

    crossterm versions

  • Dependency prometheus 0.13 is outdated

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

    prometheus versions

  • Dependency prost 0.13 is outdated

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

    prost versions

  • Dependency prost-types 0.13 is outdated

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

    prost-types versions

  • Dependency rand 0.9 is outdated

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

    rand versions

  • Dependency rand_regex 0.18 is outdated

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

    rand_regex versions

  • Dependency ratatui 0.29 is outdated

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

    ratatui versions

  • Dependency reqwest 0.12 is outdated

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

    reqwest versions

  • Dependency rusqlite 0.32 is outdated

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

    rusqlite versions

  • Dependency sha2 0.10 is a bit outdated

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

    sha2 versions

  • Dependency toml 0.8 is outdated

    Consider upgrading to 1.1.0+spec-1.1.0 to get all the fixes and improvements.

    toml versions

  • Dependency tonic 0.12 is outdated

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

    tonic versions

  • Imprecise dependency requirement clap = 4

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

    clap versions

  • Optional dependency 'http' 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 'http', 'h3-quinn', 'bytes', 'h3', 'quinn', 'prost-types', 'prost', 'rustls', 'rustls-native-certs', 'rustls-pemfile', 'tonic' may have been unintentional.

    Crate features

• rustbgpd-wire

  • Imprecise dependency requirement bytes = 1

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

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