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.

• jams-cli

  • No repository property

    Specify git repository URL in Cargo.toml to help users find more information, contribute, and for lib.rs to read more info.

  • Missing keywords

    Help users find your crates. Add keywords = ["cli-applications", "model", "interaction", "server", "deprecated"] (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.

• jams-serve

  • Dependency opentelemetry 0.22.0 is significantly outdated

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

    opentelemetry versions

  • Dependency opentelemetry-otlp 0.15.0 is significantly outdated

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

    opentelemetry-otlp versions

  • Dependency opentelemetry-semantic-conventions 0.15.0 is significantly outdated

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

    opentelemetry-semantic-conventions versions

  • Dependency opentelemetry_sdk 0.22.1 is significantly outdated

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

    opentelemetry_sdk versions

  • Dependency tracing-opentelemetry 0.23.0 is significantly outdated

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

    tracing-opentelemetry 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.

    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

  • 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 axum 0.7 is outdated

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

    axum versions

  • Dependency tonic-reflection 0.11.0 is outdated

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

    tonic-reflection versions

  • Dependency tower-http 0.5 is outdated

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

    tower-http versions

  • Missing categories

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

• jams, jams-cli, jams-core, jams-proto

  • Missing categories

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

    List of available categories

• jams-serve, jams-client, jams-proto

  • 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

• jams-proto

  • Could not fetch repository

    We've had trouble cloning git repo from https://github\.com/gagansingh894/jams\-rs\.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.

  • Dependency tonic-build 0.11.0 is significantly outdated

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

    tonic-build versions

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

  • 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 tonic-reflection 0.11.0 is outdated

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

    tonic-reflection versions

  • Missing keywords

    Help users find your crates. Add keywords = ["proto", "definations", "framework", "model", "solution"] (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.

• jams-core

  • Dependency azure_core 0.20.0 is significantly outdated

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

    azure_core 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

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

    Detecting docs.rs

  • Dependency azure_storage 0.20.0 is outdated

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

    azure_storage versions

  • Dependency azure_storage_blobs 0.20.0 is outdated

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

    azure_storage_blobs versions

  • Dependency dashmap 5.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 ndarray 0.15.6 is outdated

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

    ndarray versions

  • Dependency rand 0.8.5 is a bit outdated

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

    rand versions

  • Dependency tch 0.15.0 is outdated

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

    tch versions

  • Published crate contains binary files

    The crate contains binary files (Zip file). Crates are meant to be compiled from source. Please check that you haven't published temporary build files by accident. If you have test fixtures, consider excluding them from crates-io tarball, since Cargo doesn't run tests from crates-io packages.

    Audit page

• jams-client

  • Imprecise dependency requirement tokio = 1

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

  • Missing categories

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

    List of available categories

  • Missing keywords

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