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.

• input-linux

  • Dependency tokio-util 0.6 is significantly outdated

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

    tokio-util versions

  • Dependency nix 0.29 is outdated

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

    nix versions

  • 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

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["os::unix-apis"] 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 'bytes' 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 'bytes' may have been unintentional.

    Crate features

  • Using outdated edition for no reason

    We estimate that this crate requires at least Rust 1.69, which is newer than the last 2018-edition compiler. You can upgrade without breaking any compatibility. Run cargo fix --edition and update edition="…" in Cargo.toml.

    Using the latest edition helps avoid old quirks of the compiler, and ensures Rust code has consistent syntax and behavior across all projects.

    The Edition Guide

• input-linux-sys

  • Published crate doesn't match its repository

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

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

    • src/
      • input.rs does not match the repository.
      • uinput.rs does not match the repository.

    Fetched https://github.com/arcnmx/input-linux-sys-rs.git tagged v0.9.0 (b39046ceb4d6ae3369e7a101484b5df9cf02f5eb).

    Checked on 2024-07-28

    This check is experimental.

    Forum thread

  • Dependency nix 0.29 is outdated

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

    nix versions

• serde-value, pipe, nvapi-sys

  • 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

• serde-value, serde_ini, qapi-spec

  • Missing categories

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

    List of available categories

• serde-value

  • Dependency ordered-float ^2.0.0 is outdated

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

    ordered-float versions

• serde_ini

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

    Maintenance status field docs

• nvoclock

  • Dependency env_logger 0.4.3 is significantly outdated

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

    env_logger versions

  • Dependency log 0.3.8 is significantly outdated

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

    log versions

  • Dependency prettytable-rs 0.6.7 is significantly outdated

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

    prettytable-rs versions

  • Dependency result ^0.0.1 is significantly outdated

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

    result versions

  • Latest stable release is old

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

  • Dependency clap 2.26.2 is outdated

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

    clap versions

  • Dependency nvapi-hi 0.0.3 is slightly outdated

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

    nvapi-hi versions

  • Dependency quick-error 1.2.1 is outdated

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

    quick-error versions

• nue

  • Incorrect dependency requirement nue-io = 0.3

    We could not parse it. Please check the semver syntax.

    Cargo used to be more forgiving about the semver syntax, so it's possible that an already-published crate doesn't satisfy the current rules.

    Cargo dependencies manual

  • Incorrect dependency requirement packed = 0.3

    We could not parse it. Please check the semver syntax.

    Cargo dependencies manual

  • Incorrect dependency requirement pod = 0.3

    We could not parse it. Please check the semver syntax.

    Cargo dependencies manual

  • Dependency packed 0.3 is significantly outdated

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

    packed versions

  • Dependency pod 0.3 is significantly outdated

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

    pod versions

• input-linux-sys, nvapi, pipe, pod, cfg-match, nvapi-sys, nvoclock, packed, mosh-server-upnp, qapi-qga

  • Missing categories

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

    List of available categories

• ocf

  • Dependency syntex ^0.29.0 has issues

    It has been losing active users, which may be a sign it's deprecated or obsolete. Consider replacing it with a different crate.

    syntex crate

  • Latest prerelease is old

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

    It's an opportunity to update it to the current Rust edition.

    Maintenance status field docs

  • Dependency semver ^0.2.1 is significantly outdated

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

    semver versions

  • Dependency serde ^0.7.0 is significantly outdated

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

    serde versions

  • Dependency serde-value ^0.1.0 is significantly outdated

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

    serde-value versions

  • Dependency serde_codegen ^0.7.0 has issues

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

    serde_codegen crate

  • Dependency serde_json ^0.7.0 is significantly outdated

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

    serde_json versions

  • Dependency serde_macros ^0.7.0 has issues

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

    serde_macros crate

• cfg-match

  • README missing from the repository

    We've searched https://github\.com/arcnmx/cfg\-match\-rs\.git and could not find a README file there.

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

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

    Maintenance status field docs

• nue-codegen

  • Dependency syntex 0.7 has issues

    It has been losing active users, which may be a sign it's deprecated or obsolete. Consider replacing it with a different crate.

    syntex crate

  • Dependency syntex_syntax 0.9 has issues

    It has been losing active users, which may be a sign it's deprecated or obsolete. Consider replacing it with a different crate.

    syntex_syntax crate

  • Incorrect dependency requirement quasi = *

    We could not parse it. Please check the semver syntax.

    Cargo dependencies manual

  • Incorrect dependency requirement quasi_codegen = *

    We could not parse it. Please check the semver syntax.

    Cargo dependencies manual

  • Dependency aster 0.4 is significantly outdated

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

    aster versions

  • Dependency quasi_macros 0.3 is significantly outdated

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

    quasi_macros versions

  • Missing categories

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

    List of available categories

• resize-slice

  • Dependency smallvec 0.1 is significantly outdated

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

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

    Maintenance status field docs

• specialize

  • Latest stable release is old

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

    Nightly crates tend to have a short lifespan. We're delisting them if they're not updated frequently.

    Maintenance status field docs

• ddc

  • Could not find the crate in the repository

    Make sure the main branch of https://github\.com/arcnmx/ddc\-rs contains the Cargo.toml for the crate. If you have forked the crate, change the repository property in Cargo.toml to your fork's URL.

• pipe

  • Dependency readwrite ^0.1.1 is outdated

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

    readwrite versions

  • Using outdated edition for no reason

    We estimate that this crate requires at least Rust 1.36, which is newer than the last 2015-edition compiler. You can upgrade without breaking any compatibility. Run cargo fix --edition and update edition="…" in Cargo.toml.

    The Edition Guide

• pod, packed, uninitialized

  • Latest stable release is old

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

• pod, cfg-match, resize-slice, nvoclock, packed, uninitialized, specialize

  • The Cargo package has no git commit information

    Before publishing a package, make sure all packaged files are committed to the repository, and there are no "dirty" files. Push this commit to crate's public repository.

    To protect against supply chain attacks similar to CVE-2024-3094, lib.rs will soon start flagging non-reproducible packages without public source code as suspicious. Currently only git repositories are supported (but may be hosted anywhere, not just GitHub). If you'd like a different SCM supported, please file a feature request.

    More info

• nvapi

  • Using outdated edition for no reason

    We estimate that this crate requires at least Rust 1.37, which is newer than the last 2015-edition compiler. You can upgrade without breaking any compatibility. Run cargo fix --edition and update edition="…" in Cargo.toml.

    The Edition Guide

• nvapi-hi, nue-macros, nue-io, nue-codegen, tokio-qapi, ddcutil-sys, i2c-i2cdev

  • Buggy README path

    The non-local path to readme specified as \.\./README\.md exposes a bug in Cargo. Please use a path inside the crate's directory. Symlinks are okay. Please verify the change doesn't break any repo-relative URLs in the README.

• nvapi-hi, coalesce, ddcset, nue, result, byteorder-pod, ddcutil, tokio-qapi, ddcutil-sys, read_exact, i2c-i2cdev

  • Missing categories

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

    List of available categories

• nue-io

  • Incorrect dependency requirement uninitialized = 0.0

    We could not parse it. Please check the semver syntax.

    Cargo dependencies manual

  • Dependency byteorder 0.3 is significantly outdated

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

    byteorder versions

  • Missing categories

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

    List of available categories

• coalesce, nue, nue-macros, nue-io, ocf, nue-codegen

  • Latest stable release is old

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

• cstrptr

  • README missing from the repository

    We've searched https://github\.com/arcnmx/cstrptr\-rs\.git and could not find a README file there.

  • Using outdated edition for no reason

    We estimate that this crate requires at least Rust 1.60, which is newer than the last 2018-edition compiler. You can upgrade without breaking any compatibility. Run cargo fix --edition and update edition="…" in Cargo.toml.

    The Edition Guide

• nvapi-sys

  • Buggy README path

    The non-local path to readme specified as \.\./README\.md exposes a bug in Cargo. Please use a path inside the crate's directory. Symlinks are okay. Please verify the change doesn't break any repo-relative URLs in the README.

  • Dependency bitflags ^1.0.1 is outdated

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

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

• mosh-server-upnp

  • Dependency igd ^0.11.0 is significantly outdated

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

    igd versions

• tokio-qapi

  • Dependency bytes ^0.4.6 is significantly outdated

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

    bytes versions

  • Dependency futures ^0.1.18 has issues

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

    futures crate

  • Dependency qapi-spec ^0.2.2 is significantly outdated

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

    qapi-spec versions

  • Dependency tokio-codec ^0.1.1 has issues

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

    tokio-codec crate

  • Dependency tokio-io ^0.1.10 has issues

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

    tokio-io crate

  • Dependency qapi-qga ^0.4.0 is outdated

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

    qapi-qga versions

  • Dependency qapi-qmp ^0.4.0 is outdated

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

    qapi-qmp versions

• ddcset

  • 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

  • Dependency clap 2 is outdated

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

    clap versions

  • Dependency env_logger 0.10 is outdated

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

    env_logger versions

  • Dependency mccs-db 0.1 is slightly outdated

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

    mccs-db versions

• qapi, qapi-qmp, qapi-parser

  • Missing categories

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

    List of available categories

• nue-macros

  • Incorrect dependency requirement nue-codegen = 0.3

    We could not parse it. Please check the semver syntax.

    Cargo dependencies manual

  • Missing categories

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

    List of available categories

• mccs-db

  • Dependency serde_yaml 0.9 has issues

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

    serde_yaml crate

  • 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

• ddc-hi

  • Dependency ddc ^0.2.0 is slightly outdated

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

    ddc versions

  • Dependency mccs ^0.1.0 is a bit outdated

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

    mccs versions

  • Dependency mccs-caps ^0.1.0 is a bit outdated

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

    mccs-caps versions

  • Dependency mccs-db ^0.1.1 is slightly outdated

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

    mccs-db versions

  • Missing categories

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

    List of available categories

• resize-slice, uninitialized, specialize

  • Missing categories

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

    List of available categories

• ddc-winapi

  • Dependency ddc 0.2 is slightly outdated

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

    ddc versions

  • Dependency windows 0.58 is outdated

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

    windows versions

  • Imprecise dependency requirement widestring = 1

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

    widestring versions

  • Latest prerelease is old

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

  • Missing categories

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

    List of available categories

• nvapi-hi, coalesce, nue, result, nue-macros, nue-io, ocf, byteorder-pod, nue-codegen, i2c, ddcutil, ddcutil-sys, thread-scoped, read_exact, i2c-i2cdev

  • The Cargo package has no git commit information

    Before publishing a package, make sure all packaged files are committed to the repository, and there are no "dirty" files. Push this commit to crate's public repository.

    More info

• nvapi-hi, cstrptr, nue-macros, nue-io, nue-codegen, tokio-qapi, ddcutil-sys, i2c-i2cdev

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

• nvapi-hi, result, i2c, ddcutil, ddcutil-sys, thread-scoped, i2c-i2cdev

  • Latest stable release is old

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

• byteorder-pod

  • Dependency byteorder ^0.5.3 is significantly outdated

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

    byteorder versions

  • Latest stable release is old

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

• qapi-codegen

  • Missing categories

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

    List of available categories

• stack

  • Missing categories

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

    List of available categories

• nue-macros, ocf, nue-codegen

  • 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

• doc-cfg

  • Dependency proc-macro2 ^0.4.27 is significantly outdated

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

    proc-macro2 versions

  • Dependency quote ^0.6.11 is significantly outdated

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

    quote versions

• glib-signal

  • Dependency glib 0.19 is significantly outdated

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

    glib versions

• ddc-i2c

  • Dependency ddc 0.2 is slightly outdated

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

    ddc versions

• mccs-caps, mccs-db

  • Dependency nom 7 is a bit outdated

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

    nom versions

• i2c-linux

  • Dependency udev ^0.2.0 is outdated

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

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

    Maintenance status field docs

  • Missing categories

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

    List of available categories

• ocf, glib-signal, i2c-linux-sys

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["os::unix-apis"] to the Cargo.toml.

    List of available categories

• i2c-linux-sys

  • Using outdated edition for no reason

    We estimate that this crate requires at least Rust 1.46, which is newer than the last 2015-edition compiler. You can upgrade without breaking any compatibility. Run cargo fix --edition and update edition="…" in Cargo.toml.

    The Edition Guide

• i2c-linux-sys, i2c-linux, i2c, ddcutil

  • Dependency bitflags ^1.0.1 is outdated

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

    bitflags versions

• i2c

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["embedded", "rust-patterns"] to the Cargo.toml.

    List of available categories

• read_exact

  • Latest stable release is old

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

  • Missing keywords

    Help users find your crates. Add keywords = ["read-exact", "read", "io", "file", "full"] (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.

• thread-scoped

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

    Use OR instead of /.

    SPDX license list

  • Missing categories

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

    List of available categories

• i2c-i2cdev

  • Dependency i2cdev ^0.4.0 is outdated

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

    i2cdev versions

No issues found in: mccs

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