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.

• volo

  • Dependency nix 0.29 is outdated

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

    nix versions

  • Dependency webpki-roots 0.26 is outdated

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

    webpki-roots 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.

    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

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

    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.

    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

• linkedbytes

  • Published crate doesn't match its repository

    Partially verified 23 files (includes 2 Cargo-generated).

    Fetched https://github.com/volo-rs/linkedbytes.git 44da1e64523218ebed8b779d536e53866d1d4bc5.

    Checked on 2024-08-10

    This check is experimental.

    Forum thread

  • 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

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

  • Imprecise dependency requirement anyhow = 1

    Cargo does not always pick latest versions of dependencies! Specify the version as anyhow = "1.0.98". 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.21.1 to get all the fixes, and avoid causing duplicate dependencies in projects.

    salsa versions

  • 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

  • Dependency petgraph 0.6 is a bit outdated

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

    rustc-hash versions

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["development-tools::procedural-macro-helpers", "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

  • Failed to verify create's content against its repository

    Partially verified 30 files (includes 3 Cargo-generated).

    • warning: The crates.io package has no information about its path inside its repository.
    • warning: There is no matching git tag containing version '0.11.10'.
      • git tag v0.11.10 3260f067edad338b0106fdfba0bf6c1765b3424a; git push origin --tags

    Files in the crates.io crate compared to the repository:

    • Cargo.lock not found.

    Looked for the crate in pilota/. Fetched https://github.com/cloudwego/pilota.git 3260f067edad338b0106fdfba0bf6c1765b3424a.

    Checked on 2025-05-04

    Forum thread

• volo-http

  • Dependency hickory-resolver 0.24 is outdated

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

    hickory-resolver versions

  • Dependency sonic-rs 0.3 is a bit outdated

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

    sonic-rs versions

  • 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

  • Failed to verify create's content against its repository

    Partially verified 61 files (includes 2 Cargo-generated).

    • warning: Crate tarball has been published from a different commit than the commit tagged by git tag 'volo-0.3.1'.
      • Create git tags after comitting any changes, and commit changes after bumping versions and running cargo update.

    Looked for the crate in volo-http/. Fetched https://github.com/cloudwego/volo.git 0d3996026e3f932eeb1923d23901dda070cbada9.

    Checked on 2025-04-28

    Forum thread

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

  • Dependency tonic 0.12 is outdated

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

    tonic versions

  • Dependency tonic-web 0.12 is outdated

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

    tonic-web versions

• async_cache

  • Dependency hashbrown 0.14 is significantly outdated

    Upgrade to 0.15.3 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.98". 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

  • Published crate doesn't match its repository

    Partially verified 10 files (includes 2 Cargo-generated).

    Fetched https://github.com/purewhitewu/async_cache.git 48a74d5864fe68ae7d86d392a5c9b10f5df82de9.

    Checked on 2024-07-24

    Forum thread

  • Dependency dashmap 5 is outdated

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

    dashmap versions

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

  • Dependency serde_yaml 0.9 has issues

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

    serde_yaml crate

• pilota-thrift-parser

  • The Cargo package has no git commit information

    Before publishing a package, make sure all packaged files are committed to the repository, and there are no "dirty" files. Push this commit to crate's public repository.

    To protect against supply chain attacks similar to CVE-2024-3094, lib.rs will soon start flagging non-reproducible packages without public source code as suspicious. Currently only git repositories are supported (but may be hosted anywhere, not just GitHub). If you'd like a different SCM supported, please file a feature request.

    More info

  • Dependency nom 7 is a bit outdated

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

    nom versions

• faststr

  • Dependency redis 0.29 is outdated

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

    redis versions

  • 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 = ["data-structures"] to the Cargo.toml.

    List of available categories

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

    Crate features

• volo-cli

  • Dependency colored 2 is a bit outdated

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

    colored versions

  • 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

  • Failed to verify create's content against its repository

    Partially verified 36 files (includes 3 Cargo-generated).

    • warning: The crates.io package has no information about its path inside its repository.

    Files in the crates.io crate compared to the repository:

    • Cargo.lock not found.

    Looked for the crate in volo-cli/. Fetched https://github.com/cloudwego/volo.git 2b9b79c0e2a0b9ec66d91770efa04b3deb036b9b.

    Checked on 2025-04-27

    Forum thread

• volo-build

  • 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-concurrency-limiter

  • Missing categories

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

    List of available categories

  • Dependency volo 0.8 is significantly outdated

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

    volo versions

  • Latest stable release is old

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

  • Published crate doesn't match its repository

    Partially verified 23 files (includes 2 Cargo-generated).

    Fetched https://github.com/volo-rs/concurrency-limiter.git 38059bd53bf0514abf62d82e3121a6c624987f45.

    Checked on 2024-08-10

    Forum thread

  • 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.8 to get all the fixes, and avoid causing duplicate dependencies in projects.

    volo-thrift versions

  • Missing keywords

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

• volo-thrift

  • Dependency sonic-rs 0.3 is a bit outdated

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

    sonic-rs versions

• protobuf-parse2

  • Latest prerelease is old

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

  • Published crate doesn't match its repository

    Partially verified 46 files (includes 3 Cargo-generated).

    Files in the crates.io crate compared to the repository:

    • Cargo.lock not found.

    Looked for the crate in protobuf-parse/. Fetched https://github.com/lyf1999/rust-protobuf.git 62cc0326fa6c84323f973362d350b7521ca695d0.

    Checked on 2024-08-10

    Forum thread

  • Dependency indexmap 1.8.0 is outdated

    Upgrade to 2.9.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 outdated

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

    which versions

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["protobuf", "protobuf-parse2", "name"] (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.3 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

• motore-macros

  • Imprecise dependency requirement syn = 2

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

• volo-macros, volo-rt, 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.

• grpc-proxy

  • Dependency anyhow =1.0.62 is significantly outdated

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

    anyhow versions

  • Dependency futures =0.3.23 is significantly outdated

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

    futures versions

  • Dependency http =0.2.8 is significantly outdated

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

    http versions

  • Dependency hyper =0.14.20 is significantly outdated

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

    hyper versions

  • Dependency index_list =0.2.7 is significantly outdated

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

    index_list versions

  • Dependency metainfo =0.6.2 is significantly outdated

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

    metainfo versions

  • Dependency tokio =1.20.1 is significantly outdated

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

    tokio versions

  • Dependency tower-layer =0.3.1 is significantly outdated

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

    tower-layer versions

  • Dependency tracing =0.1.36 is significantly outdated

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

    tracing versions

  • Locked dependency version anyhow =1.0.62

    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.

    anyhow versions

  • Locked dependency version futures =0.3.23

    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.

    futures versions

  • Locked dependency version http =0.2.8

    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.

    http versions

  • Locked dependency version hyper =0.14.20

    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.

    hyper versions

  • Locked dependency version index_list =0.2.7

    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.

    index_list versions

  • Locked dependency version metainfo =0.6.2

    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.

    metainfo versions

  • Locked dependency version motore =0.2.1

    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.

    motore versions

  • Locked dependency version newtype =0.2.1

    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.

    newtype versions

  • Locked dependency version tokio =1.20.1

    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.

    tokio versions

  • Locked dependency version tower =0.4.13

    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.

    tower versions

  • Locked dependency version tower-layer =0.3.1

    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.

    tower-layer versions

  • Locked dependency version tracing =0.1.36

    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.

    tracing versions

  • Locked dependency version volo =0.2.1

    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.

    volo versions

  • Locked dependency version volo-grpc =0.2.1

    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.

    volo-grpc versions

  • The Cargo package has no git commit information

    Before publishing a package, make sure all packaged files are committed to the repository, and there are no "dirty" files. Push this commit to crate's public repository.

    More info

  • docs.rs build failed

    docs.rs site failed to build the crate, so users will have trouble finding the documentation. Docs.rs supports multiple platforms and custom configurations, so you can make the build work even if normal crate usage has special requirements.

    Docs.rs doesn't need to run or even link any code, so system dependencies can simply be skipped. You can also set cfg() flags just for docs.rs and use them to hide problematic code.

    Detecting docs.rs

  • Dependency motore =0.2.1 is outdated

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

    motore versions

  • Dependency tower =0.4.13 is outdated

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

    tower versions

  • Dependency volo =0.2.1 is outdated

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

    volo versions

  • Dependency volo-grpc =0.2.1 is outdated

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

    volo-grpc versions

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["proxy", "grpc", "grpc-proxy"] (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.

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