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.

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

• edge-http

  • Dependency base64 ^0.22 is a bit outdated

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

    base64 versions

  • Missing keywords

    Help users find your crates. Add keywords = ["web-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 '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' 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.14". 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-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-http, edge-raw, edge-mdns, edge-ws, edge-captive

  • Imprecise dependency requirement defmt = ^1

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

    defmt versions

• channel-bridge

  • Dependency embedded-io ^0.6 is significantly outdated

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

    embedded-io versions

  • Dependency prost ^0.11 is significantly outdated

    Upgrade to 0.14.4 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.229". 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.

    serde versions

  • Dependency edge-ws ^0.4 is outdated

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

    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-async ^0.6 is outdated

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

    embedded-io-async 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

• 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.11 to get all the fixes and improvements.

    env_logger versions

• ldproxy

  • Could not find the crate in the repository

    Make sure the main branch of https://github\.com/esp\-rs/embuild 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.

  • Dependency env_logger ^0.9 is significantly outdated

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

    env_logger versions

• edge-executor

  • 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

  • Dependency futures-lite ^1 is significantly outdated

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

    futures-lite 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

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

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

  • Dependency embassy-sync ^0.5 is significantly outdated

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

    embassy-sync versions

  • Dependency embedded-svc ^0.27 is significantly 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.4 is significantly outdated

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

    gloo-net versions

  • Dependency strum ^0.25 is significantly outdated

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

    strum versions

  • Dependency strum_macros ^0.25 is significantly outdated

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

    strum_macros versions

  • Dependency derive_more ^0.99 is outdated

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

    derive_more versions

  • Dependency yew ^0.21 is outdated

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

    yew versions

  • Dependency yew-router ^0.18 is outdated

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

    yew-router versions

  • Dependency yewdux ^0.10 is outdated

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

    yewdux versions

  • Dependency yewdux-middleware ^0.3 is slightly outdated

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

    yewdux-middleware versions

  • Incorrect category

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

  • Optional dependency 'yewdux' 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 'yewdux', 'serde', 'derive_more', 'futures', 'yew-router', 'gloo-net', 'num_enum', 'strum_macros', 'log', 'enumset', 'strum', 'flate2', 'anyhow', 'heapless', 'embassy-sync', 'yew', 'postcard', 'wasm-bindgen-futures', 'embedded-svc', 'wasm-bindgen', 'wasm-logger', 'web-sys', 'yewdux-middleware' may have been unintentional.

    Crate features

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

  • 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

• cargo-pio, ldproxy, edge-frame

  • Imprecise dependency requirement anyhow = ^1

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

    anyhow versions

• edge-ws

  • Missing keywords

    Help users find your crates. Add keywords = ["no-std", "protocols", "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

• 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

  • Dependency embedded-io-async ^0.6 is outdated

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

    embedded-io-async 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", "traits", "tcp-socket", "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.

• hal-sim

  • Dependency embassy-sync ^0.5 is significantly outdated

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

    embassy-sync versions

  • Dependency gloo-net ^0.4 is significantly outdated

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

    gloo-net versions

  • Dependency itertools ^0.11 is significantly outdated

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

    itertools versions

  • Dependency channel-bridge ^0.8 is slightly outdated

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

    channel-bridge versions

  • Dependency embedded-hal ^0.2 is outdated

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

    embedded-hal versions

  • Dependency gloo-timers ^0.3 is a bit outdated

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

    gloo-timers versions

  • Dependency yew ^0.21 is outdated

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

    yew versions

  • Dependency yewdux ^0.10 is outdated

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

    yewdux versions

  • Dependency yewdux-middleware ^0.3 is slightly outdated

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

    yewdux-middleware versions

  • Imprecise dependency requirement nb = ^1

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

    nb versions

  • Optional dependency 'embedded-hal-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-hal-async', 'nb', 'yewdux', 'futures', 'itertools', 'gloo-net', 'embassy-futures', 'channel-bridge', 'embedded-hal02', 'embedded-graphics-core', 'yew', 'embedded-hal', 'embassy-sync', 'wasm-bindgen-futures', 'wasm-bindgen', 'wasm-logger', 'web-sys', 'yewdux-middleware', 'gloo-timers' may have been unintentional.

    Crate features

• edge-captive

  • Missing keywords

    Help users find your crates. Add keywords = ["dns", "async", "no-std", "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

• edge-executor, edge-frame, channel-bridge, hal-sim

  • Dependency heapless ^0.8 is outdated

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

    heapless versions

• rs-matter-macros

  • Dependency syn ^2 is outdated

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

    syn versions

  • Imprecise dependency requirement proc-macro-crate = ^3

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

    proc-macro-crate versions

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

  • Crate contains junk files

    The crate contains boilerplate Rust files with no real functionality.

• mbedtls-rs-sys

  • Internal error

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

• nrf-802154-sys

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

• matter-rs-macros

  • Crate contains junk files

    The crate contains boilerplate Rust files with no real functionality.

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

• edge-net

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/edge-net ) 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-nal-tls

  • Internal error

    We couldn't check this crate at this time, because: timed out validating Origin( lib.rs/crates/edge-nal-tls ). 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.

• rs-matter-stack

  • Internal error

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

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

• edge-nal

  • Internal error

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

• openthread

  • Internal error

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

• mbedtls-rs

  • Internal error

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

• nrf-802154

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

• espsign

  • Internal error

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

• esp-idf-hal

  • Internal error

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

• embuild

  • Internal error

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

• edge-mqtt

  • Internal error

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

• esp-idf-svc

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/esp-idf-svc ) 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-std-nal-async

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/edge-std-nal-async ) failed. 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.

• openthread-sys

  • Internal error

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

• edge-nal-openthread

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/edge-nal-openthread ) 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.