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.

• embuild, ldproxy, cargo-pio, espsign

  • Imprecise dependency requirement anyhow = 1

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

• embedded-svc

  • Dependency strum 0.27 is outdated

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

    strum versions

  • Dependency strum_macros 0.27 is outdated

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

    strum_macros versions

  • Imprecise dependency requirement enumset = 1

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

    enumset versions

  • Optional dependency 'strum_macros' 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 'strum_macros', 'strum', 'num_enum' may have been unintentional.

    Crate features

• async-io-mini

  • Imprecise dependency requirement enumset = 1

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

    enumset versions

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

    Crate features

• edge-nal

  • Missing keywords

    Help users find your crates. Add keywords = ["udp-socket", "tcp-socket", "embedded-nal-async", "no-alloc"] (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.

• embuild

  • Dependency bindgen 0.71.1 is significantly outdated

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

    bindgen versions

  • Dependency cargo_toml 0.15 is significantly outdated

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

    cargo_toml versions

  • Dependency globwalk 0.8 is significantly outdated

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

    globwalk versions

  • Dependency remove_dir_all 0.8 is significantly outdated

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

    remove_dir_all versions

  • Dependency toml 0.7 is significantly outdated

    Upgrade to 1.1.0+spec-1.1.0 to get all the fixes, and avoid causing duplicate dependencies in projects.

    toml versions

  • Dependency bitflags 1 is outdated

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

    bitflags versions

  • Dependency strum 0.24 is significantly outdated

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

    strum versions

  • Dependency thiserror 1 is outdated

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

    thiserror versions

  • Dependency ureq 2 is outdated

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

    ureq versions

  • Dependency which 4.1 is outdated

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

    which versions

  • Dependency xmas-elf 0.9 is outdated

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

    xmas-elf versions

• channel-bridge

  • Dependency prost 0.11 is significantly outdated

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

    prost versions

  • Imprecise dependency requirement serde = 1

    Cargo does not always pick latest versions of dependencies! Specify the version as serde = "1.0.228". 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 edge-ws 0.4 is outdated

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

    edge-ws versions

  • Dependency embassy-sync 0.6 is outdated

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

    embassy-sync versions

  • Dependency embedded-io 0.6 is slightly outdated

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

    embedded-io versions

  • Dependency embedded-svc 0.28 is outdated

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

    embedded-svc versions

  • Dependency gloo-net 0.6 is a bit outdated

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

    gloo-net versions

  • Optional dependency 'embedded-io-async' 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 'embedded-io-async', 'futures', 'gloo-net', 'embassy-futures', 'log', 'embedded-io', 'heapless', 'postcard' may have been unintentional.

    Crate features

• edge-executor

  • Dependency futures-lite 1 is significantly outdated

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

    futures-lite versions

  • Dependency portable-atomic-util 0.1 is significantly outdated

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

    portable-atomic-util versions

  • Imprecise dependency requirement atomic-waker = 1

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

    atomic-waker versions

  • Optional dependency 'heapless' 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 'heapless', 'portable-atomic-util' may have been unintentional.

    Crate features

• cargo-pio

  • Dependency structopt 0.3.22 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.

    structopt crate

  • Dependency env_logger 0.9 is significantly outdated

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

    env_logger versions

• esptools

  • Dependency directories 3 is significantly outdated

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

    directories 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

  • Dependency reqwest 0.12 is outdated

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

    reqwest versions

  • Dependency sha1 0.10 is a bit outdated

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

    sha1 versions

  • Dependency zip 2 is outdated

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

    zip versions

  • Imprecise dependency requirement flate2 = 1

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

    flate2 versions

  • Imprecise dependency requirement zip = 2

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

    zip versions

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

    Crate features

• edge-mdns

  • Dependency domain 0.11 is outdated

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

    domain versions

  • Dependency embassy-sync 0.7 is outdated

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

    embassy-sync versions

  • Dependency rand_core 0.9 is outdated

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

    rand_core versions

  • Missing keywords

    Help users find your crates. Add keywords = ["mdns-responder", "async", "no-alloc"] (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.

  • Optional dependency 'embassy-sync' 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 'embassy-sync', 'edge-nal', 'embassy-futures', 'embassy-time' may have been unintentional.

    Crate features

• openthread-sys

  • Latest stable release is old

    It's been over 5 years. How did the experiment go? 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 bindgen 0.53.1 is significantly outdated

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

    bindgen versions

  • 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

  • Published crate contains binary files

    The crate contains binary files (obscure autoconf code). Crates are meant to be compiled from source. Please check that you haven't published temporary build files by accident. If you have test fixtures, consider excluding them from crates-io tarball, since Cargo doesn't run tests from crates-io packages.

    Audit page

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

• edge-http

  • Dependency embassy-sync 0.7 is outdated

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

    embassy-sync versions

  • Missing keywords

    Help users find your crates. Add keywords = ["web-server", "async", "no-alloc"] (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.

  • Optional dependency 'embedded-io-async' 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 'embedded-io-async', 'embassy-sync', 'edge-nal', 'embassy-futures', 'embassy-time' may have been unintentional.

    Crate features

• edge-raw

  • Missing keywords

    Help users find your crates. Add keywords = ["udp", "udp-packet", "async", "no-alloc"] (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.

  • Optional dependency 'edge-nal' 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 'edge-nal', 'embedded-io-async' may have been unintentional.

    Crate features

• edge-mqtt

  • Dependency rumqttc 0.23 is significantly outdated

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

    rumqttc versions

  • Dependency embedded-svc 0.28 is outdated

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

    embedded-svc versions

  • Failed to verify create's content against its repository

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

    • warning: Crate tarball has been published from a different commit than the commit tagged by git tag 'v0.4.0'.
      • Create git tags after comitting any changes, and commit changes after bumping versions and running cargo update.
    • warning: Repository fetch error: Broken repo: protocol error, missing OIDs or HEAD.
      • Ooops? If this shouldn't happen, file a bug https://gitlab.com/lib.rs/main

    Looked for the crate in edge-mqtt/. Fetched https://github.com/ivmarkov/edge-net.git tagged v0.9.0 (4efdbb218bdf98fde281c12f0a03456b20612a9d).

    Checked on 2025-01-05

    This check is experimental.

    Forum thread

  • Missing keywords

    Help users find your crates. Add keywords = ["mqtt-client", "rumqttc", "async", "traits", "embedded-svc"] (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.

• embedded-nal-async-xtra

  • Dependency embedded-nal-async 0.7 is significantly outdated

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

    embedded-nal-async versions

  • Incorrect category

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

  • Missing keywords

    Help users find your crates. Add keywords = ["embedded-nal-async", "udp-multicast", "traits", "networking"] (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.

• edge-captive

  • Dependency domain 0.11 is outdated

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

    domain versions

  • Missing keywords

    Help users find your crates. Add keywords = ["dns", "dns-server", "no-alloc"] (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.

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

    Crate features

• ldproxy

  • Dependency embuild 0.32 is outdated

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

    embuild versions

  • Dependency env_logger 0.9 is significantly outdated

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

    env_logger versions

• edge-std-nal-async

  • Dependency embedded-nal-async 0.7 is significantly outdated

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

    embedded-nal-async versions

  • Dependency futures-lite 1 is significantly outdated

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

    futures-lite versions

  • Imprecise dependency requirement async-io = 2

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

  • Incorrect category

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["embedded-nal-async", "async-std", "embedded-nal-async-xtra", "networking"] (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.

• edge-ws

  • Missing keywords

    Help users find your crates. Add keywords = ["async", "websocket", "no-alloc"] (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.

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

    Crate features

• espsign

  • Dependency num-bigint-dig 0.8.2 is slightly outdated

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

    num-bigint-dig versions

  • Dependency rand 0.8 is outdated

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

    rand versions

  • Dependency rand_core 0.6 is outdated

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

    rand_core versions

  • Dependency sha2 0.10 is a bit outdated

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

    sha2 versions

  • Optional dependency 'rand' 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 'rand', 'anyhow', 'env_logger', 'clap' may have been unintentional.

    Crate features

• edge-executor, channel-bridge, edge-std-nal-async

  • Dependency heapless 0.8 is outdated

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

    heapless versions

• channel-bridge, embedded-nal-async-xtra, espsign, edge-std-nal-async

  • Dependency embedded-io-async 0.6 is a bit outdated

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

    embedded-io-async versions

• openthread

  • Missing categories

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

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

  • Published crate doesn't match its repository

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

    Fetched https://github.com/ivmarkov/openthread.git 229bf418390d88202de8d06c3b7e6377961a933f.

    Checked on 2025-03-16

    Forum thread

  • Missing keywords

    Help users find your crates. Add keywords = ["reservation", "bindings", "mcu-agnostic", "embassy-net", "coming"] (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.

• rs-matter-macros

  • Failed to verify create's content against its repository

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

    • warning: The crates.io package has no information about its path inside its repository.
    • warning: There is no matching git tag containing version '0.1.0'.
      • git tag v0.1.0 ede024cf712186cdef8ff7175ab664d830e3769b; git push origin --tags

    Looked for the crate in rs-matter-macros/. Fetched https://github.com/project-chip/matter-rs.git ede024cf712186cdef8ff7175ab664d830e3769b.

    Checked on 2024-08-10

    Forum thread

  • Dependency syn 1 is significantly outdated

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

    syn versions

  • Imprecise dependency requirement syn = 1

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

  • Dependency proc-macro-crate 1.3 is outdated

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

    proc-macro-crate versions

• matter-rs, esp-idf-matter, rs-matter-embassy, rs-matter-stack, matter-rs-macros

  • Crate contains junk files

    The crate contains boilerplate Rust files with no real functionality.

• nrf-802154

  • Crate is 'reserved'

    Please be respectful of crates.io and don't squat crate names.

    It's OK if you intend to publish this project in the near future. Keep in mind that even if you have good intentions, things may not go as planned. crates.io won't reclaim abandoned crates, so reserving good names may end up wasting the good names.

  • No readme property

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

• nrf-802154-sys

  • Crate is 'reserved'

    Please be respectful of crates.io and don't squat crate names.

  • No readme property

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

• edge-nal-std

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/edge-nal-std ) failed. Please try again later.

• esp-idf-sys

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/esp-idf-sys ) failed. Please try again later.

• esp-idf-hal

  • Internal error

    We couldn't check this crate at this time, because: timed out validating Origin( lib.rs/crates/esp-idf-hal ). Please try again later.

• esp-idf-svc

  • Internal error

    We couldn't check this crate at this time, because: timed out validating Origin( lib.rs/crates/esp-idf-svc ). Please try again later.

• hal-sim

  • Internal error

    We couldn't check this crate at this time, because: timed out getting crate for validation Origin( lib.rs/crates/hal-sim ). Please try again later.

• edge-frame

  • Internal error

    We couldn't check this crate at this time, because: timed out getting crate for validation Origin( lib.rs/crates/edge-frame ). Please try again later.

• yewdux-middleware

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/yewdux-middleware ) failed. Please try again later.

• rs-matter

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/rs-matter ) failed. Please try again later.

• edge-dhcp

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/edge-dhcp ) failed. Please try again later.

• edge-net

  • Internal error

    We couldn't check this crate at this time, because: timed out validating Origin( lib.rs/crates/edge-net ). Please try again later.

• edge-nal-embassy

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/edge-nal-embassy ) failed. Please try again later.

No issues found in: gfx-xtra

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