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.

• fe2o3-amqp

  • Dependency sha-1 0.10 has issues

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

    sha-1 crate

  • Dependency getrandom 0.2 is outdated

    Consider upgrading to the latest version 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.

    getrandom versions

  • Dependency rand 0.8 is a bit outdated

    Consider upgrading to the latest version to get all the fixes and improvements.

    rand versions

  • Dependency thiserror 1 is a bit outdated

    Consider upgrading to the latest version to get all the fixes and improvements.

    thiserror versions

  • Imprecise dependency requirement bytes = 1

    Cargo does not always pick latest versions of dependencies! 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.

    bytes 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

  • Optional dependency 'webpki-roots' 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 'webpki-roots', 'pbkdf2', 'rand', 'uuid', 'libnative-tls', 'stringprep', 'base64', 'tokio-rustls', 'tokio-native-tls', 'sha2', 'ring', 'sha-1', 'librustls', 'hmac' may have been unintentional.

    Crate features

• serde_amqp

  • Published crate doesn't match its repository

    Verified 39 out of 41 files (includes 2 Cargo-generated).

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

    • Readme.md exists, but elsewhere in the repo.

    Looked for the crate in serde_amqp/. Fetched https://github.com/minghuaw/fe2o3-amqp.git 269127daa5aac10799a5c1fa740d8f41fa68a74d.

    Checked on 2024-12-29

    This check is experimental.

    Forum thread

  • Dependency ordered-float 4 is outdated

    Upgrade to the latest version 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 the latest version to get all the fixes and improvements.

    thiserror versions

  • Imprecise dependency requirement bytes = 1

    Cargo does not always pick latest versions of dependencies! 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

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

    Crate features

• azservicebus

  • Dependency azure_core 0.20 is significantly outdated

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

    azure_core versions

  • Dependency fe2o3-amqp 0.10 is outdated

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

    fe2o3-amqp versions

  • Dependency fe2o3-amqp-cbs 0.10 is a bit outdated

    Consider upgrading to the latest version to get all the fixes and improvements.

    fe2o3-amqp-cbs versions

  • Dependency fe2o3-amqp-management 0.10 is outdated

    Consider upgrading to the latest version to get all the fixes and improvements.

    fe2o3-amqp-management versions

  • Dependency fe2o3-amqp-types 0.10 is outdated

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

    fe2o3-amqp-types versions

  • Dependency fe2o3-amqp-ws 0.10 is slightly outdated

    Consider upgrading to the latest version to get all the fixes and improvements.

    fe2o3-amqp-ws versions

  • Dependency getrandom 0.2 is outdated

    Consider upgrading to the latest version to get all the fixes and improvements.

    getrandom versions

  • Dependency rand 0.8.5 is a bit outdated

    Consider upgrading to the latest version to get all the fixes and improvements.

    rand versions

  • Dependency serde_amqp 0.10 is outdated

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

    serde_amqp versions

  • Dependency thiserror 1.0 is a bit outdated

    Consider upgrading to the latest version to get all the fixes and improvements.

    thiserror versions

  • Imprecise dependency requirement indexmap = 2

    Cargo does not always pick latest versions of dependencies! 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.

    indexmap versions

• fe2o3-amqp, serde_amqp, fe2o3-amqp-cbs

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

    Use OR instead of /.

    SPDX license list

• mlx-sys

  • *-sys crate without links property

    If this crate uses C libraries with public symbols, consider adding links = "mlx" to crate's Cargo.toml to avoid other libraries colliding with them. Note that the links property adds exclusivity to dependency resolution, but doesn't do any linking.

    This is also needed to protect your crate from duplicate older versions of itself. C symbols are global, and duplicate symbols can cause all sorts of breakage.

  • Dependency bindgen 0.70 is outdated

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

    bindgen versions

  • Imprecise dependency requirement cc = 1

    Cargo does not always pick latest versions of dependencies! 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.

    cc 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

• mlx-internal-macros

  • Could not fetch repository

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

  • Imprecise dependency requirement syn = 2

    Cargo does not always pick latest versions of dependencies! 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.

    syn versions

  • No readme property

    Specify path to a README file for the project, so that information about is included in the crates.io tarball.

• mlx-macros

  • Could not fetch repository

    We've had trouble cloning git repo from https://github\.com/oxideai/mlx\-rs\.git

  • Imprecise dependency requirement syn = 2

    Cargo does not always pick latest versions of dependencies! 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

  • No readme property

    Specify path to a README file for the project, so that information about is included in the crates.io tarball.

• fe2o3-amqp-cbs

  • Missing categories

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

    List of available categories

• mlx-rs, fe2o3-amqp-management, fe2o3-amqp-ws, fe2o3-amqp-ext, fe2o3-amqp-types, serde_amqp_derive, azeventhubs, toy-rpc, piscina, timer-kit, toy-rpc-macros, brw

  • Internal error

    We couldn't check this crate at this time, because: deadline has elapsed. Please try again later.

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