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.

• const_fixedp

  • Latest stable release is old

    It's been over 3 years. How did the experiment go? 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

  • Imprecise dependency requirement serde = 1

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

    serde versions

• threescalers

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

    anyhow versions

  • Dependency http ^0.2 is outdated

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

    http versions

  • Dependency reqwest >= 0.10, < 0.12 is outdated

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

    reqwest versions

  • Dependency serde-xml-rs ^0.4 is outdated

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

    serde-xml-rs 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

• limitador

  • Dependency tonic 0.11 is significantly outdated

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

    tonic versions

  • Dependency tonic-build 0.11 is significantly outdated

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

    tonic-build versions

  • Dependency dashmap 5.5.3 is outdated

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

    dashmap versions

  • Dependency getrandom 0.2 is outdated

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

    getrandom versions

  • Dependency h2 0.3 is a bit outdated

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

    h2 versions

  • Dependency metrics 0.22.3 is outdated

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

    metrics versions

  • Dependency prost 0.12 is outdated

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

    prost versions

  • Dependency prost-types 0.12 is significantly outdated

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

    prost-types versions

  • Dependency redis 0.25 is outdated

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

    redis versions

  • Dependency rocksdb 0.22 is outdated

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

    rocksdb versions

  • Dependency tonic-reflection 0.11 is outdated

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

    tonic-reflection versions

  • Imprecise dependency requirement tokio = 1

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

    tokio versions

  • Optional dependency 'tonic' 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 'tonic', 'tokio', 'rocksdb', 'base64', 'r2d2', 'tokio-stream', 'tonic-reflection', 'redis', 'prost-types', 'h2', 'prost', 'uuid' may have been unintentional.

    Crate features

• infinispan

  • Imprecise dependency requirement serde = 1

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

    serde versions

  • Dependency base64 0.13 is outdated

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

    base64 versions

  • Dependency http 0.2 is outdated

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

    http versions

  • Dependency reqwest 0.11 is outdated

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

    reqwest 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

• const_fixedp, limitador, infinispan

  • Dependency thiserror 1 is a bit outdated

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

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