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.
sysfs_gpio
Dependency mio 0.8 is significantly outdated
Upgrade to 1.0.3 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.Dependency nix 0.23 is significantly outdated
Upgrade to 0.29.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.
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.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.Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["embedded"]
to theCargo.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.
Missing keywords
Help users find your crates. Add
keywords = ["linux-gpio", "gpio-pin", "linux-kernel", "raspberry-pi", "embedded-linux"]
(up to 5) to theCargo.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.
gpio-utils
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.Dependency env_logger 0.5 is significantly outdated
Upgrade to 0.11.6 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency error-chain 0.12 has issues
It may not be actively developed any more. Consider changing the dependency.
Dependency glob 0.2 is significantly outdated
Upgrade to 0.3.2 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency nix 0.11 is significantly outdated
Upgrade to 0.29.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency toml 0.4 is significantly outdated
Upgrade to 0.8.20 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency users 0.8 is significantly outdated
Upgrade to 0.11.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency clap 2.2 is outdated
Upgrade to 4.5.31 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency sysfs_gpio 0.5.2 is a bit outdated
Consider upgrading to 0.6.2 to get all the fixes and improvements.
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"
).If the crate is truly stable, why not make a 1.0.0 release?
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["embedded"]
to theCargo.toml
.
gpio-cdev
Dependency nix 0.27 is significantly outdated
Upgrade to 0.29.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
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.Optional dependency 'futures' 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 'futures', 'tokio' may have been unintentional.
sysfs-pwm
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.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"
).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.
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["os::unix-apis"]
to theCargo.toml
.Missing keywords
Help users find your crates. Add
keywords = ["pwm", "interface", "sysfs", "pin", "linux"]
(up to 5) to theCargo.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.
spidev
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["os::unix-apis"]
to theCargo.toml
.Missing keywords
Help users find your crates. Add
keywords = ["spi", "interface", "linux", "devices", "access"]
(up to 5) to theCargo.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.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 updateedition="…"
inCargo.toml
.Using the latest edition helps avoid old quirks of the compiler, and ensures Rust code has consistent syntax and behavior across all projects.
i2cdev
Dependency nix 0.26.2 is outdated
Upgrade to 0.29.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Imprecise dependency requirement byteorder = 1
Cargo does not always pick latest versions of dependencies! Specify the version as
byteorder = "1.5.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.Using outdated edition for no reason
We estimate that this crate requires at least Rust 1.56, which is newer than the last 2015-edition compiler. You can upgrade without breaking any compatibility. Run
cargo fix --edition
and updateedition="…"
inCargo.toml
.
spidev, sysfs_gpio, i2cdev, gpio-utils, sysfs-pwm
License MIT/Apache-2.0 is not in SPDX syntax
Use
OR
instead of/
.
If some of these crates are unmaintained and shouldn't be checked, yank them or add [badges.maintenance]
to their
status = "deprecated"Cargo.toml
.