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.

• web-push

  • Dependency http 0.2 is outdated

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

    Easy way to bump dependencies: cargo install cargo-edit; cargo upgrade -i; Also check out Dependabot service on GitHub.

    http versions

  • Dependency hyper 0.14 is outdated

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

    hyper versions

  • Dependency hyper-tls 0.5 is outdated

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

    hyper-tls versions

  • Optional dependency 'futures-lite' 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 'futures-lite', 'hyper', 'isahc', 'hyper-tls' may have been unintentional.

    Crate features

• tiberius, graphql-composition, grafbase-sql-ast, faunadb, mongodb-data-api, quaint

  • Missing categories

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

• grafbase-sdk

  • Dependency time 0.3.41 is significantly outdated

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

    time versions

  • Published crate doesn't match its repository

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

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

    • Cargo.lock not found.

    Looked for the crate in crates/grafbase-sdk/. Fetched https://github.com/grafbase/grafbase.git 561a33ad0d7ae4b0bd960394162f6139a42d1b05.

    Checked on 2025-04-28

    This check is experimental.

    Forum thread

  • Dependency async-tungstenite 0.28.0 is outdated

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

    async-tungstenite versions

  • Imprecise dependency requirement http = 1

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

    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.

    http versions

• grafbase-sdk-mock

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

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

    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

  • Missing keywords

    Help users find your crates. Add keywords = ["extension", "mocking", "grafbase-sdk-mock"] (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.

• grafbase-sql-ast

  • Failed to verify create's content against its repository

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

    • warning: Crate tarball has been published from the commit 715444492ed334b890003f2fb0defc42c3ff9b92, which is not in the repository.
      • Create git tags after comitting any changes, and commit changes after bumping versions and running cargo update.
    • warning: Could not find any matching commit in the repository. Used latest commit as a fallback. The results may be incorrect.
    • warning: Had to perform fuzzy search of the head branch due to lack of commit information in the package.
    • error: Manifest properties don't match: Existence of [lib] inconsistent: published=true; orig=false.

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

    • .gitignore does not match the repository.
    • README.md does not match the repository.
    • LICENSE does not match the repository.
    • flake.nix does not match the repository.
    • flake.lock does not match the repository.
    • Cargo.toml.orig does not match the repository.
    • rust-toolchain.toml does not match the repository.
    • test.yml not found.
    • src/
      • ast.rs not found.
      • lib.rs not found.
      • renderer.rs not found.
    • src/ast/
      • expression.rs not found.
      • over.rs not found.
      • ordering.rs not found.
      • select.rs not found.
      • update.rs not found.
      • row.rs not found.
      • conditions.rs not found.
      • column.rs not found.
      • common_table_expression.rs not found.
      • values.rs not found.
      • query.rs not found.
      • compare.rs not found.
      • grouping.rs not found.
      • insert.rs not found.
      • join.rs not found.
      • delete.rs not found.
      • function.rs not found.
      • conjunctive.rs not found.
      • ops.rs not found.
      • table.rs not found.
    • src/ast/function/
      • upper.rs not found.
      • encode.rs not found.
      • json_build_object.rs not found.
      • average.rs not found.
      • sum.rs not found.
      • json_extract_array.rs not found.
      • count.rs not found.
      • row_number.rs not found.
      • to_jsonb.rs not found.
      • json_agg.rs not found.
      • coalesce.rs not found.
      • row_to_json.rs not found.
      • minimum.rs not found.
      • concat.rs not found.
      • json_extract.rs not found.
      • maximum.rs not found.
      • json_unquote.rs not found.
      • aggregate_to_string.rs not found.
      • lower.rs not found.
    • postgres.rs not found.

    Fetched https://github.com/grafbase/grafbase.git 3ad2d643ec78e65142886f30a983efa850247987.

    Checked on 2024-08-04

    Forum thread

  • 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

• faunadb

  • Latest prerelease is old

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

    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

  • Dependency async-std 0.99.5 has issues

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

    async-std crate

  • Dependency base64 0.10 is significantly outdated

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

    base64 versions

  • Dependency base64-serde 0.3 is significantly outdated

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

    base64-serde versions

  • Dependency failure 0.1 has issues

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

    failure crate

  • Dependency failure_derive 0.1 has issues

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

    failure_derive crate

  • Dependency futures-preview 0.3.0-alpha.18 has issues

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

    futures-preview crate

  • Dependency http 0.1 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.13.0-alpha.1 is significantly outdated

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

    hyper versions

  • Dependency hyper-tls 0.4.0-alpha.1 is significantly outdated

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

    hyper-tls versions

• tiberius

  • Dependency async-io 1.8 is significantly outdated

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

    async-io versions

  • Dependency async-std 1 has issues

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

    async-std crate

  • Dependency async-native-tls 0.4 is outdated

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

    async-native-tls versions

  • Dependency async-net 1.7 is outdated

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

    async-net versions

  • Dependency asynchronous-codec 0.6 is outdated

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

    asynchronous-codec versions

  • Dependency bigdecimal 0.3 is outdated

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

    bigdecimal versions

  • Dependency futures-lite 1.12.0 is outdated

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

    futures-lite versions

  • Dependency libgssapi 0.4.5 is outdated

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

    libgssapi versions

  • Dependency pretty-hex 0.3 is outdated

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

    pretty-hex versions

  • Dependency rustls-native-certs 0.6 is outdated

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

    rustls-native-certs versions

  • Dependency rustls-pemfile 1 is outdated

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

    rustls-pemfile versions

  • Dependency thiserror 1.0 is a bit outdated

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

    thiserror versions

  • Dependency tokio-rustls 0.24.0 is outdated

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

    tokio-rustls versions

  • Dependency winauth 0.0.4 is slightly outdated

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

    winauth versions

  • Imprecise dependency requirement async-std = 1

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

    async-std versions

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

    Use OR instead of /.

    SPDX license list

• mongodb-data-api

  • Dependency tracing-subscriber 0.2 is significantly outdated

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

    tracing-subscriber 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

  • Published crate doesn't match its repository

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

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

    • Cargo.lock does not match the repository.

    Fetched https://github.com/grafbase/mongodb-data-api.git 8c5124bf55c4ce02964965900b43bc6b5ad99257.

    Checked on 2024-08-10

    Forum thread

  • Dependency axum 0.6.20 is outdated

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

    axum versions

  • Dependency base64 0.21.2 is outdated

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

    base64 versions

  • Dependency mongodb 2.6.0 is outdated

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

    mongodb versions

• xorc-notifications

  • Missing categories

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

    List of available categories

  • Dependency base64 0.6 is significantly outdated

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

    base64 versions

  • Dependency bytes 0.4 is significantly outdated

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

    bytes versions

  • Dependency chan 0.1 has issues

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

    chan crate

  • Dependency chan-signal 0.3 has issues

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

    chan-signal crate

  • Dependency futures 0.1 has issues

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

    futures crate

  • Dependency http 0.1 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.12 is significantly outdated

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

    hyper versions

  • Dependency hyper-tls 0.3 is significantly outdated

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

    hyper-tls versions

  • Dependency prometheus 0.4 is significantly outdated

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

    prometheus versions

  • Dependency rdkafka 0.17 is significantly outdated

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

    rdkafka versions

  • Dependency time 0.1 is significantly outdated

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

    time versions

  • Dependency tokio 0.1 has issues

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

    tokio crate

  • Dependency tokio-signal 0.1 has issues

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

    tokio-signal crate

  • Dependency tokio-timer 0.1 has issues

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

    tokio-timer crate

  • Dependency toml 0.4 is significantly outdated

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

    toml versions

  • Latest stable release is old

    It's been over 6 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

  • Dependency a2 0.3 is slightly outdated

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

    a2 versions

  • Dependency erased-serde 0.3 is outdated

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

    erased-serde versions

  • Dependency fcm 0.6 is outdated

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

    fcm versions

  • Dependency heck 0.3 is outdated

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

    heck versions

  • Dependency protobuf 2.0 is outdated

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

    protobuf versions

  • Dependency web-push 0.4 is outdated

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

    web-push versions

  • Imprecise dependency requirement regex = 1

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

    regex versions

• graphql-federated-graph, grafbase-sdk-mock, grafbase-sdk-derive, grafbase-hooks-derive

  • No readme property

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

• fcm

  • Imprecise dependency requirement serde = 1

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

  • Dependency erased-serde 0.3 is outdated

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

    erased-serde versions

  • Dependency reqwest 0.11.0 is outdated

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

    reqwest versions

  • Missing categories

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

    List of available categories

• graphql-federated-graph

  • Failed to verify create's content against its repository

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

    • warning: Crate tarball has been published from a different commit than the commit tagged by git tag 'sdk-0.7.1'.
      • Create git tags after comitting any changes, and commit changes after bumping versions and running cargo update.

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

    • Cargo.lock not found.

    Looked for the crate in crates/graphql-federated-graph/. Fetched https://github.com/grafbase/grafbase.git 344bc91b4aa77007baad41882d790e8fbef188c3.

    Checked on 2025-04-30

    Forum thread

  • Imprecise dependency requirement bitflags = 2

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

    bitflags versions

  • Missing categories

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

    List of available categories

• connection-string

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["connection-string", "string", "escaping", "connection", "wasm"] (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.

• grafbase-sdk, grafbase-hooks, grafbase-sdk-mock

  • Missing categories

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

    List of available categories

• graphql-composition

  • Imprecise dependency requirement bitflags = 2

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

    bitflags versions

• grafbase-hooks

  • Failed to verify create's content against its repository

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

    • warning: Crate tarball has been published from a different commit than the commit tagged by git tag '0.4.1'.
      • Create git tags after comitting any changes, and commit changes after bumping versions and running cargo update.

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

    • Cargo.lock not found.

    Looked for the crate in crates/grafbase-hooks/. Fetched https://github.com/grafbase/grafbase.git d0b973590cfbb6cc62dad6cec644a1e786951b52.

    Checked on 2025-04-27

    Forum thread

• opentls

  • Incorrect category

    Crate's categories property in Cargo.toml contains 'openssl', 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

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

    Maintenance status field docs

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

    Use OR instead of /.

    SPDX license list

  • Missing keywords

    Help users find your crates. Add keywords = ["tls", "openssl", "opentls"] (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.

• faunadb, xorc-notifications, quaint

  • 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

• grafbase-sdk-derive

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

  • Imprecise dependency requirement syn = 2

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

• grafbase-hooks-derive

  • Failed to verify create's content against its repository

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

    • warning: The crates.io package has no information about its path inside its repository.
    • warning: Could not find Cargo.toml for this package in its repo (via tags).
      • Make sure the repository URL in Cargo.toml is correct
    • warning: Could not discover crate's location in its repository (via tags).
    • warning: Could not find any matching commit in the repository. Used latest commit as a fallback. The results may be incorrect.

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

    • Cargo.toml.orig does not match the repository.
    • src/
      • expand.rs not found.
      • lib.rs not found.

    Fetched https://github.com/grafbase/grafbase.git 7fe1318720d20730d2ebb4b653ffc3e2aab5a789.

    Checked on 2024-12-01

    Forum thread

• quaint

  • Dependency base64 0.11.0 is significantly outdated

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

    base64 versions

  • Dependency bytes 0.5 is significantly outdated

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

    bytes versions

  • Dependency libsqlite3-sys 0.17 is significantly outdated

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

    libsqlite3-sys versions

  • Dependency metrics 0.12 is significantly outdated

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

    metrics versions

  • Dependency mysql_async 0.23 is significantly outdated

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

    mysql_async versions

  • Dependency postgres-native-tls 0.3 is significantly outdated

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

    postgres-native-tls versions

  • Dependency rusqlite 0.21 is significantly outdated

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

    rusqlite versions

  • Dependency tiberius 0.4 is significantly outdated

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

    tiberius versions

  • Dependency tokio 0.2 has issues

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

    tokio crate

  • Dependency tokio-postgres 0.5 is significantly outdated

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

    tokio-postgres versions

  • Dependency tokio-util 0.3 is significantly outdated

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

    tokio-util versions

  • Dependency uuid 0.8 is significantly outdated

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

    uuid versions

  • Dependency bit-vec 0.6.1 is outdated

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

    bit-vec versions

  • Dependency mobc 0.5.7 is significantly outdated

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

    mobc versions

  • Dependency thiserror 1.0 is a bit outdated

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

    thiserror versions

  • Imprecise dependency requirement percent-encoding = 2

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

    percent-encoding versions

No issues found in: local-atlas-data-api

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