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.

• actix-storage

  • Dependency quick-xml 0.26.0 is significantly outdated

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

    quick-xml versions

  • Dependency serde_yaml 0.8 has issues

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

    serde_yaml crate

  • Dependency bincode 1.3 is slightly outdated

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

    bincode versions

  • Dependency ron 0.8.0 is outdated

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

    ron versions

• actix-storage, basteh, actix-storage-hashmap, actix-storage-dashmap, actix-storage-sled, basteh-memory, actix-storage-redis, basteh-redis

  • Dependency thiserror 1 is a bit outdated

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

    thiserror versions

• serde-querystring-actix

  • Published crate doesn't match its repository

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

    Looked for the crate in serde-querystring-actix/. Fetched https://github.com/pooyamb/serde-querystring.git f2c95ad67482e550029ef7f8bc8aa03fc6234f7a.

    Checked on 2025-02-16

    This check is experimental.

    Forum thread

  • Dependency derive_more 0.99 is outdated

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

    derive_more versions

  • Imprecise dependency requirement actix-web = ^4

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

    actix-web versions

• seaqs

  • Dependency sea-query 0.28 is significantly outdated

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

    sea-query versions

  • Dependency utoipa 3 is significantly outdated

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

    utoipa versions

  • Dependency serde_with 2.1 is outdated

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

    serde_with versions

  • Imprecise dependency requirement utoipa = 3

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

    utoipa versions

  • Optional dependency 'sea-query' 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 'sea-query', 'utoipa' may have been unintentional.

    Crate features

• actix-storage, actix-storage-hashmap, actix-storage-dashmap, actix-storage-sled, basteh-memory, actix-storage-redis

  • 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

• basteh-redb

  • Latest prerelease is old

    It's been over 20 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 13 files (includes 2 Cargo-generated).

    Looked for the crate in basteh-redb/. Fetched https://github.com/pooyamb/basteh.git 36188c0a416232703385352d1656229feb35dc57.

    Checked on 2024-08-10

    Forum thread

  • Dependency priority-queue 1.3 is a bit outdated

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

    priority-queue versions

  • Dependency redb 1.0 is outdated

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

    redb versions

• basteh

  • Published crate doesn't match its repository

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

    Looked for the crate in basteh/. Fetched https://github.com/pooyamb/basteh.git d3832d5dba0168ab7f8b8777b8fa11b621b08bac.

    Checked on 2024-07-28

    Forum thread

• basteh, basteh-memory, basteh-redis

  • Latest prerelease is old

    It's been over 2 years. 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").

    Maintenance status field docs

• actix-storage-sled

  • Dependency actix 0.10 is significantly outdated

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

    actix versions

  • Dependency zerocopy 0.3 is significantly outdated

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

    zerocopy versions

  • Dependency actix-storage 0.2.0 is outdated

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

    actix-storage versions

  • Latest stable release is old

    It's been over 4 years. 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").

    If the crate is truly stable, why not make a 1.0.0 release?

    Maintenance status field docs

• json-resp

  • Dependency utoipa 3 is significantly outdated

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

    utoipa versions

  • Imprecise dependency requirement serde_json = 1

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

    serde_json versions

  • Dependency axum 0.6 is outdated

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

    axum versions

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

    Crate features

• basteh, basteh-redb, basteh-redis

  • 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

• serde-querystring-axum

  • Dependency axum-core 0.3.0 is outdated

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

    axum-core versions

  • Dependency http 0.2 is outdated

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

    http versions

• basteh-memory

  • Published crate doesn't match its repository

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

    Looked for the crate in basteh-memory/. Fetched https://github.com/pooyamb/basteh.git d3832d5dba0168ab7f8b8777b8fa11b621b08bac.

    Checked on 2024-07-24

    Forum thread

• basteh-redis

  • Published crate doesn't match its repository

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

    Looked for the crate in basteh-redis/. Fetched https://github.com/pooyamb/basteh.git d3832d5dba0168ab7f8b8777b8fa11b621b08bac.

    Checked on 2024-07-28

    Forum thread

  • Dependency redis 0.22 is outdated

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

    redis versions

• actix-storage-dashmap

  • Dependency dashmap 5.3.4 is outdated

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

    dashmap versions

• actix-storage-redis

  • Dependency redis 0.22 is outdated

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

    redis versions

• json-resp-derive

  • Dependency syn 1.0.96 is significantly outdated

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

    syn versions

No issues found in: serde-querystring

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