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.
dumb-crypto, bulk-gcd, tokio-lock
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"
).Users pay attention to the latest release date. Even if the crate is perfectly fine as-is, users may not know that.
naught
Latest prerelease 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"
).Dependency futures ^0.1.25 has issues
It may not be actively developed any more. Consider changing the dependency.
Dependency hyper ^0.12.24 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 rand ^0.6.5 is significantly outdated
Upgrade to 0.9.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.
Dependency tokio-sync ^0.1.1 has issues
It may not be actively developed any more. Consider changing the dependency.
Dependency twox-hash ^1.1.2 is slightly outdated
Consider upgrading to 2.1.0 to get all the fixes and improvements.
Missing keywords
Help users find your crates. Add
keywords = ["tba", "tbd", "why"]
(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.
bulk-gcd
Dependency env_logger ^0.6.0 is significantly outdated
Upgrade to 0.11.6 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency clap ^2.32.0 is outdated
Upgrade to 4.5.31 to get all the fixes, and avoid causing duplicate dependencies in projects.
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.
append-log
Latest prerelease 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"
).
tokio-lock
Dependency futures ^0.1.25 has issues
It may not be actively developed any more. Consider changing the dependency.
Dependency tokio ^0.1.15 has issues
It may not be actively developed any more. Consider changing the dependency.
Missing keywords
Help users find your crates. Add
keywords = ["tokio-task", "object", "single"]
(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.
better-blockmap
Dependency clap 3.1.5 is significantly outdated
Upgrade to 4.5.31 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency base64 0.13.0 is outdated
Upgrade to 0.22.1 to get all the fixes, and avoid causing duplicate dependencies in projects.
If some of these crates are unmaintained and shouldn't be checked, yank them or add [badges.maintenance]
to their
status = "deprecated"Cargo.toml
.