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.
ftdi-embedded-hal
Imprecise dependency requirement nb = 1
Cargo does not always pick latest versions of dependencies! Specify the version as
nb = "1.1.0"
. IfCargo.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 theminimal-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.Optional dependency 'libftd2xx' 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 'libftd2xx', 'ftdi' may have been unintentional.
ftdi-embedded-hal, w5500-ll
Dependency embedded-hal 0.2.7 is a bit outdated
Consider upgrading to 1.0.0 to get all the fixes and improvements.
Easy way to bump dependencies:
cargo install cargo-edit; cargo upgrade -i
; Also check out Dependabot service on GitHub.
ftd2xx-embedded-hal
Latest stable release is old
It's been over 3 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?
Reported security advisory RUSTSEC-2022-0005
crate has been renamed to `ftdi-embedded-hal`
Dependency embedded-hal ~0.2.4 is a bit outdated
Consider upgrading to 1.0.0 to get all the fixes and improvements.
Dependency libftd2xx ~0.31.0 is outdated
Upgrade to 0.33.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.
Imprecise dependency requirement nb = ^1
Cargo does not always pick latest versions of dependencies! Specify the version as
nb = "1.1.0"
. IfCargo.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 theminimal-versions
flag, used by users of old Rust versions.
w5500-regsim
Dependency trust-dns-client 0.23 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.
libftd2xx-ffi
Dependency bindgen ~0.70.1 is outdated
Upgrade to 0.71.1 to get all the fixes, and avoid causing duplicate dependencies in projects.
Needs more categories
Please more specific categories that describe functionality of the crate. Expand
categories = ["hardware-support", "external-ffi-bindings"]
in yourCargo.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.
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.
oidc_pages
Dependency scraper 0.22.0 is outdated
Consider upgrading to 0.23.1 to get all the fixes and improvements.
bme280-multibus
Imprecise dependency requirement serde = 1
Cargo does not always pick latest versions of dependencies! Specify the version as
serde = "1.0.218"
. IfCargo.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 theminimal-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.
Dependency embedded-hal 0.2.7 is a bit outdated
Consider upgrading to 1.0.0 to get all the fixes and improvements.
stm32wlxx-hal
Dependency embedded-hal 0.2.6 is a bit outdated
Consider upgrading to 1.0.0 to get all the fixes and improvements.
Dependency rand_core 0.6 is a bit outdated
Consider upgrading to 0.9.2 to get all the fixes and improvements.
Imprecise dependency requirement nb = 1
Cargo does not always pick latest versions of dependencies! Specify the version as
nb = "1.1.0"
. IfCargo.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 theminimal-versions
flag, used by users of old Rust versions.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.
w5500-hl
Dependency embedded-hal-mock 0.10.0 is outdated
Upgrade to 0.11.1 to get all the fixes, and avoid causing duplicate dependencies in projects.
w5500-mqtt, w5500-dns, w5500-tls, w5500-dhcp
Dependency rand_core 0.6 is a bit outdated
Consider upgrading to 0.9.2 to get all the fixes and improvements.
w5500-tls
Imprecise dependency requirement subtle = 2
Cargo does not always pick latest versions of dependencies! Specify the version as
subtle = "2.6.0"
. IfCargo.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 theminimal-versions
flag, used by users of old Rust 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.
Dependency ftdi-embedded-hal 0.21 is outdated
Upgrade to 0.22.1 to get all the fixes, and avoid causing duplicate dependencies in projects.
hackrfone
Dependency rusb ~0.8 is significantly outdated
Upgrade to 0.9.4 to get all the fixes, and avoid causing duplicate dependencies in projects.
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"
).
corsairmi
Imprecise dependency requirement tokio = 1
Cargo does not always pick latest versions of dependencies! Specify the version as
tokio = "1.43.0"
. IfCargo.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 theminimal-versions
flag, used by users of old Rust versions.
w5500-embassy, w5500-https, w5500-http, w5500-ntp
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.
No issues found in: clap-num ftdi-mpsse libftd2xx w5500-sntp p256-cm4 lora-e5-bsp nucleo-wl55jc-bsp stm32wl-hal
If some of these crates are unmaintained and shouldn't be checked, yank them or add [badges.maintenance]
to their
status = "deprecated"Cargo.toml
.