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.

• ringhash

  • Missing categories

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

  • Imprecise dependency requirement thiserror = 1

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

    thiserror versions

  • Published crate doesn't match its repository

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

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

    • Cargo.lock not found.

    Fetched https://github.com/millione/ringhash.git 83466443904c8c2bd494734f888c6395e9221e23.

    Checked on 2024-08-10

    This check is experimental.

    Forum thread

  • Dependency dashmap 5 is outdated

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

    dashmap versions

  • Dependency thiserror 1 is a bit outdated

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

    thiserror versions

• static-graph

  • Dependency heck 0.4 is outdated

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

    heck versions

  • Dependency nom 7 is a bit outdated

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

    nom versions

  • Imprecise dependency requirement arc-swap = 1

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

    arc-swap versions

  • Missing categories

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

    List of available categories

• typedcache

  • Published crate doesn't match its repository

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

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

    • Cargo.lock not found.

    Fetched https://github.com/millione/typedcache.git 5606e36562f0bedb97aa2ed82d101cf89835bf16.

    Checked on 2024-08-10

    Forum thread

  • 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 arc-swap = 1

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

    arc-swap versions

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["development-tools::build-utils"] to the Cargo.toml.

    List of available categories

• await-group

  • Published crate doesn't match its repository

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

    Fetched https://github.com/millione/await-group.git dbd318a772a365a1bf5bc30c96d86e6e15ed347d.

    Checked on 2024-08-04

    Forum thread

  • Imprecise dependency requirement atomic-waker = 1

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

    atomic-waker versions

  • Missing categories

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

    List of available categories

• static-graph, typedcache, ringhash, await-group

  • License MIT/Apache-2.0 is not in SPDX syntax

    Use OR instead of /.

    SPDX license list

• shmipc

  • 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

    Verified 50 out of 51 files (includes 3 Cargo-generated).

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

    • Cargo.lock not found.
    • Cargo.toml.orig does not match the repository.
    • Cargo.toml exists, but elsewhere in the repo.

    Fetched https://github.com/cloudwego/shmipc-rs.git 417b8345e1bef2edc0439e1deee4801968ba8223.

    Checked on 2025-03-16

    Forum thread

  • Dependency nix 0.29 is outdated

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

    nix versions

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

    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

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

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