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.

• rudis-http

  • Published crate doesn't match its repository

    Verified 14 out of 15 files (includes 2 Cargo-generated).

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

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

    Fetched https://github.com/lorenzoc25/rudis.git 4ca18159c74aafb4fe87e1f61b9c7725bd4cdedc.

    Checked on 2024-07-24

    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.

    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

  • Incorrect category

    Crate's categories property in Cargo.toml contains 'http', which isn't a category we recognize

    lib.rs has simplified and merged some of crates.io categories. Please file a bug if we got it wrong.

    List of available categories

  • Incorrect category

    Crate's categories property in Cargo.toml contains 'server', which isn't a category we recognize

    List of available categories

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