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.

• metainfo

  • Imprecise dependency requirement rustc-hash = 2

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

    rustc-hash versions

  • Optional dependency 'tokio' 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 'tokio' may have been unintentional.

    Crate features

• motore

  • Dependency tower 0.4 is outdated

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

    tower versions

  • Imprecise dependency requirement pin-project = 1

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

    pin-project versions

• volo

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

    once_cell versions

• pilota, volo-thrift, volo-cli, volo-grpc, volo-build, pilota-build

  • 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

• pilota-build

  • Dependency salsa 0.17.0-pre.2 is significantly outdated

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

    salsa versions

  • Dependency petgraph 0.6 is a bit outdated

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

    petgraph versions

  • Dependency rustc-hash 1 is a bit outdated

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

    rustc-hash versions

  • Missing categories

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

• pilota

  • Dependency ordered-float 4 is outdated

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

    ordered-float versions

  • Dependency thiserror 1 is a bit outdated

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

    thiserror versions

• async_cache

  • Dependency hashbrown 0.14 is significantly outdated

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

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

    anyhow versions

  • Dependency dashmap 5 is outdated

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

    dashmap versions

• volo-cli, volo-build, pilota-build

  • Dependency serde_yaml 0.9 has issues

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

    serde_yaml crate

• volo-grpc

  • 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

• linkedbytes, volo-http

  • Imprecise dependency requirement bytes = 1

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

• volo-build

  • Dependency dirs 5 is outdated

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

    dirs versions

  • Dependency git2 0.19 is outdated

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

    git2 versions

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["encoding", "development-tools::procedural-macro-helpers"] to the Cargo.toml.

    List of available categories

• volo-http

  • Dependency tokio-tungstenite 0.24 is outdated

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

    tokio-tungstenite versions

  • Dependency tungstenite 0.24 is outdated

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

    tungstenite versions

• faststr

  • Imprecise dependency requirement bytes = 1

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

  • Missing categories

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

    List of available categories

  • Optional dependency 'ryu' 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 'ryu', 'itoa' may have been unintentional.

    Crate features

• pilota-thrift-parser, volo-build

  • Dependency nom 7 is a bit outdated

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

    nom versions

• volo-cli

  • Dependency colored 2 is a bit outdated

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

    colored versions

• volo-cli, volo-build, pilota-build

  • Dependency itertools 0.13 is outdated

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

    itertools versions

• volo-concurrency-limiter

  • Missing categories

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

    List of available categories

  • Latest stable release is old

    It's been over 14 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").

    Nightly crates tend to have a short lifespan. We're delisting them if they're not updated frequently.

    Maintenance status field docs

  • Dependency volo 0.8 is significantly outdated

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

    volo versions

  • Dependency volo-grpc 0.8 is outdated

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

    volo-grpc versions

  • Dependency volo-thrift 0.8 is outdated

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

    volo-thrift versions

  • Missing keywords

    Help users find your crates. Add keywords = ["volo", "limiter", "service", "concurrency", "layer"] (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.

• motore-macros

  • Dependency syn 1 is significantly outdated

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

    syn versions

  • Imprecise dependency requirement syn = 1

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

    syn versions

• protobuf-parse2

  • Dependency indexmap 1.8.0 is outdated

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

    indexmap versions

  • Dependency thiserror 1.0.30 is a bit outdated

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

    thiserror versions

  • Dependency which 4.0 is a bit outdated

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

    which versions

  • Latest prerelease is old

    It's been over 15 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

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["protobuf", "proto-file", "serialization", "file-descriptor", "descriptor-set"] (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.

• async_singleflight

  • Dependency hashbrown 0.13 is significantly outdated

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

    hashbrown versions

  • Imprecise dependency requirement pin-project = 1

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

    pin-project versions

• volo-macros

  • Could not fetch repository

    We've had trouble cloning git repo from https://github\.com/cloudwego/volo\.git

    At the moment we only support git, and attempt fetching when we index a new release. Cloning is necessary for lib.rs to gather data that is missing on crates.io, e.g. to correctly resolve relative URLs in README files, which depend on repository layout and non-standard URL schemes of repository hosts.

• volo-macros, volo-rt, grpc-proxy, opensergo, opensergo-rs

  • README missing from crate tarball

    Cargo sometimes fails to package the README file. Ensure the path to the README in Cargo.toml is valid, and points to a file inside the crate's directory.

• is-even-or-odd

  • Imprecise dependency requirement is-odd = 1

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

    is-odd versions

  • Missing categories

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

    List of available categories

• volo-rt, grpc-proxy, tik, opensergo, opensergo-rs

  • Crate contains junk files

    The crate contains boilerplate Rust files with no real functionality.

No issues found in: fastcache

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