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-world
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.
Latest stable release is old
It's been over 5 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?
rsworld
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["…"]
to theCargo.toml
.Latest stable release is old
It's been over 5 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"
).
rsworld-sys
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["…"]
to theCargo.toml
.*-sys crate without links property
If this crate uses C libraries with public symbols, consider adding
links = "rsworld"
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.
Latest stable release is old
It's been over 5 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"
).Published crate contains binary files
The crate contains binary files (Cab file). 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.
If some of these crates are unmaintained and shouldn't be checked, yank them or add [badges.maintenance]
to their
status = "deprecated"Cargo.toml
.