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.
rust-mio
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["…"]
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.
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 bindgen 0.59.1 is significantly outdated
Upgrade to 0.71.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.
README missing from crate tarball
Cargo sometimes fails to package the
README
file. Ensure the path to theREADME
inCargo.toml
is valid, and points to a file inside the crate's directory.Dependency run_script 0.6.3 is outdated
Upgrade to 0.11.0 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"
).If the crate is truly stable, why not make a 1.0.0 release?
Missing keywords
Help users find your crates. Add
keywords = ["state-machine", "param", "index", "motr"]
(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, ELF lib). 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.
Using outdated edition for no reason
We estimate that this crate requires at least Rust 1.46, which is newer than the last 2015-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.
rust_motr
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 bindgen 0.59.1 is significantly outdated
Upgrade to 0.71.1 to get all the fixes, and avoid causing duplicate dependencies in projects.
README missing from crate tarball
Cargo sometimes fails to package the
README
file. Ensure the path to theREADME
inCargo.toml
is valid, and points to a file inside the crate's directory.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.Dependency run_script 0.6.3 is outdated
Upgrade to 0.11.0 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"
).Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["algorithms"]
to theCargo.toml
.Missing keywords
Help users find your crates. Add
keywords = ["state-machine", "param", "index", "read", "motr"]
(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.
If some of these crates are unmaintained and shouldn't be checked, yank them or add [badges.maintenance]
to their
status = "deprecated"Cargo.toml
.