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.
libstorage
Dependency cookie ~0.11 is significantly outdated
Upgrade to 0.18.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.
Dependency csv ~1.0 is significantly outdated
Upgrade to 1.3.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 futures ~0.1 has issues
It may not be actively developed any more. Consider changing the dependency.
Dependency hyper ~0.12 is significantly outdated
Upgrade to 1.6.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency nom ~3.2 is significantly outdated
Upgrade to 8.0.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency quick-xml ~0.12 is significantly outdated
Upgrade to 0.37.5 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency rayon ~1.0 is significantly outdated
Upgrade to 1.10.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency reqwest ~0.9 is significantly outdated
Upgrade to 0.12.15 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency simplelog ~0.5 is significantly outdated
Upgrade to 0.12.2 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency tokio-core ~0.1 has issues
It may not be actively developed any more. Consider changing the dependency.
Dependency uuid ~0.7 is significantly outdated
Upgrade to 1.16.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency xml-rs ~0.7 is significantly outdated
Upgrade to 0.8.26 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency influx_db_client ~0.3 is outdated
Consider upgrading to 0.6.1 to get all the fixes and improvements.
Dependency treexml ~0.6 is outdated
Upgrade to 0.7.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 categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["web-programming::http-server"]
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.
libstorage, point-derive, xml-attributes-derive
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.
point-derive
Dependency proc-macro2 0.4 is significantly outdated
Upgrade to 1.0.95 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency quote ~0.6 is significantly outdated
Upgrade to 1.0.40 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency syn ~0.15 is significantly outdated
Upgrade to 2.0.101 to get all the fixes, and avoid causing duplicate dependencies in projects.
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"
).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.
xml-attributes-derive
Dependency proc-macro2 ~0.2 is significantly outdated
Upgrade to 1.0.95 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency quote ~0.4 is significantly outdated
Upgrade to 1.0.40 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency syn ~0.12 is significantly outdated
Upgrade to 2.0.101 to get all the fixes, and avoid causing duplicate dependencies in projects.
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"
).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.
If some of these crates are unmaintained and shouldn't be checked, yank them or add [badges.maintenance]
to their
status = "deprecated"Cargo.toml
.