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.
aws-iot-device-sdk
Dependency rand 0.8 is a bit outdated
Consider upgrading to 0.9.1 to get all the fixes and improvements.
In Cargo, different 0.x versions are considered incompatible, so this is a semver-major upgrade.
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["network-programming"]
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 = ["aws-iot", "iot", "aws-sdk", "unofficial", "devices"]
(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.
aws-greengrass-nucleus
Dependency aws-config 0.48.0 is significantly outdated
Upgrade to 1.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.Dependency aws-sdk-s3 0.18.0 is significantly outdated
Upgrade to 1.83.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency aws-types 0.48.0 is significantly outdated
Upgrade to 1.3.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency clap 3 is significantly outdated
Upgrade to 4.5.37 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency rumqttc 0.16 is significantly outdated
Upgrade to 0.24.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency serde_yaml 0.9 has issues
It may not be actively developed any more. Consider changing the dependency.
Imprecise dependency requirement anyhow = 1
Cargo does not always pick latest versions of dependencies! Specify the version as
anyhow = "1.0.98"
. 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.
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.
Dependency aws-sdk-greengrassv2 0.18.0 is slightly outdated
Consider upgrading to 1.66.0 to get all the fixes and improvements.
Dependency aws-sdk-iot 0.18.0 is slightly outdated
Consider upgrading to 1.75.0 to get all the fixes and improvements.
Dependency dashmap 5 is outdated
Consider upgrading to 6.1.0 to get all the fixes and improvements.
Dependency reqwest 0.11 is outdated
Upgrade to 0.12.15 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency thiserror 1.0.34 is a bit outdated
Consider upgrading to 2.0.12 to get all the fixes and improvements.
aws-iot-device-sdk, aws-iot-ffi, core-mqtt-agent, core-mqtt-sys, aws-iot-device-client
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.
aws-iot-ffi, core-mqtt-agent, core-mqtt-sys, aws-iot-device-client
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["…"]
to theCargo.toml
.
aws-iot-ffi
Published crate doesn't match its repository
Partially verified 7 files (includes 2 Cargo-generated).
Fetched
https://github.com/awsa2ron/aws-iot-ffi.git
6ce3c7a9b71b08be7dd1f6d97d528d91c0e49a2e.Checked on 2024-08-10
This check is experimental.
Missing keywords
Help users find your crates. Add
keywords = ["aws-iot-ffi", "path", "iot", "security", "unofficial"]
(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.
core-mqtt-agent
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.Missing keywords
Help users find your crates. Add
keywords = ["unofficial", "agent", "mqtt"]
(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.
core-mqtt-sys
Dependency bindgen 0.59 is significantly outdated
Upgrade to 0.71.1 to get all the fixes, and avoid causing duplicate dependencies in projects.
*-sys crate without links property
If this crate uses C libraries with public symbols, consider adding
links = "core-mqtt"
to crate'sCargo.toml
to avoid other libraries colliding with them. Note that the links property adds exclusivity to dependency resolution, but doesn't do any linking.This is also needed to protect your crate from duplicate older versions of itself. C symbols are global, and duplicate symbols can cause all sorts of breakage.
Missing keywords
Help users find your crates. Add
keywords = ["mqtt", "core-mqtt-sys", "unofficial", "update", "build"]
(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.Published crate contains binary files
The crate contains binary files (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.
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.
aws-iot-device-client
Dependency clap 3.0 is significantly outdated
Upgrade to 4.5.37 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency rumqttc 0.10.0 is significantly outdated
Upgrade to 0.24.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency toml 0.5 is outdated
Upgrade to 0.8.22 to get all the fixes, and avoid causing duplicate dependencies in projects.
Missing keywords
Help users find your crates. Add
keywords = ["aws-iot-device-client", "iot", "aws-iot", "unofficial"]
(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.
core-mqtt-agent, core-mqtt-sys, aws-iot-device-client
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"
).If the crate is truly stable, why not make a 1.0.0 release?
No issues found in: aws-iot-device-sdk-embedded aws-iot-device-sdk-embedded-rust aws-iot-embedded-sdk
If some of these crates are unmaintained and shouldn't be checked, yank them or add [badges.maintenance]
to their
status = "deprecated"Cargo.toml
.