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.

• libftd2xx-ffi

  • Dependency bindgen ~0.70.1 is significantly outdated

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

    bindgen versions

  • Needs more categories

    Please more specific categories that describe functionality of the crate. Expand categories = ["hardware-support", "external-ffi-bindings"] in your 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

  • Published crate contains binary files

    The crate contains binary files (DOS exe, ELF exe/lib, static library). 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

• w5500-hl, w5500-dns, w5500-ll, w5500-dhcp, w5500-sntp

  • Dependency defmt 0.3.8 is outdated

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

    defmt versions

• ftd2xx-embedded-hal

  • Latest stable release is old

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

  • Reported security advisory RUSTSEC-2022-0005

    crate has been renamed to `ftdi-embedded-hal`

    All crate audits

  • Dependency embedded-hal ~0.2.4 is outdated

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

    embedded-hal versions

  • Dependency libftd2xx ~0.31.0 is outdated

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

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

    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.

    nb versions

• stm32wlxx-hal

  • Dependency defmt 0.3 is outdated

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

    defmt versions

  • Dependency embedded-hal 0.2.6 is outdated

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

    embedded-hal 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 stm32wl 0.15.1 is a bit outdated

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

    stm32wl 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

  • Latest stable release is old

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

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

    Crate features

• bme280-multibus

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

    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 embedded-hal 0.2.7 is outdated

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

    embedded-hal versions

• tls-tester

  • Dependency hkdf 0.12.4 is slightly outdated

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

    hkdf versions

  • Dependency hmac 0.12.1 is a bit outdated

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

    hmac versions

  • Dependency rand 0.8 is outdated

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

    rand versions

  • Dependency sha2 0.10.8 is a bit outdated

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

    sha2 versions

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["tls", "server", "tester", "client", "documentation"] (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.

• w5500-ll

  • Dependency embedded-hal 0.2.7 is outdated

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

    embedded-hal versions

• eeprom25aa02e48

  • Dependency embedded-hal-mock 0.10 is outdated

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

    embedded-hal-mock versions

  • Dependency ftdi-embedded-hal 0.21 is outdated

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

    ftdi-embedded-hal versions

• corsairmi

  • Imprecise dependency requirement tokio = 1

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

    tokio versions

• w5500-embassy, w5500-ntp, w5500-https, w5500-http

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

• rak3172-bsp

  • Crate contains junk files

    The crate contains boilerplate Rust files with no real functionality.

• ftdi-embedded-hal

  • Internal error

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

• oidc_pages

  • Internal error

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

• libftd2xx

  • Internal error

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

• w5500-mqtt

  • Internal error

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

• w5500-tls

  • Internal error

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

• nucleo-wl55jc-bsp

  • Internal error

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

• lora-e5-bsp

  • Internal error

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

No issues found in: hackrfone p256-cm4 clap-num ftdi-mpsse w5500-regsim stm32wl-hal

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