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.
argonautica
Dependency base64 0.10 is significantly outdated
Upgrade to 0.22.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 bindgen 0.48 is significantly outdated
Upgrade to 0.71.1 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency cfg-if 0.1 is significantly outdated
Upgrade to 1.0.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 criterion 0.2 is significantly outdated
Upgrade to 0.5.1 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency failure 0.1 has issues
It may not be actively developed any more. Consider changing the dependency.
Dependency futures 0.1 has issues
It may not be actively developed any more. Consider changing the dependency.
Dependency futures-cpupool 0.1 has issues
It may not be actively developed any more. Consider changing the dependency.
Dependency md5 0.6 is significantly outdated
Upgrade to 0.7.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency nom 4.2 has issues
It may not be actively developed any more. Consider changing the dependency.
Dependency rand 0.6 is significantly outdated
Upgrade to 0.9.1 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency rust-argon2 0.4.0 is significantly outdated
Upgrade to 2.1.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency sha2 0.8 is significantly outdated
Upgrade to 0.10.8 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency tempdir 0.3 has issues
It may not be actively developed any more. Consider changing the dependency.
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"
).If the crate is truly stable, why not make a 1.0.0 release?
Dependency bitflags 1.0 is outdated
Upgrade to 2.9.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
num-format, argonautica, num-format-windows, argonautica-c
License MIT/Apache-2.0 is not in SPDX syntax
Use
OR
instead of/
.
urls2disk
Dependency cfg-if 0.1 is significantly outdated
Upgrade to 1.0.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency clippy 0.0 has issues
It may not be actively developed any more. Consider changing the dependency.
Dependency crossbeam 0.3 is significantly outdated
Upgrade to 0.8.4 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency failure 0.1 has issues
It may not be actively developed any more. Consider changing the dependency.
Dependency reqwest 0.8 is significantly outdated
Upgrade to 0.12.15 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency url 1.7 is significantly outdated
Upgrade to 2.5.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Latest stable release is old
It's been over 7 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"
).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.
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.
num-format-windows
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.
Dependency bindgen 0.63.0 is significantly outdated
Upgrade to 0.71.1 to get all the fixes, and avoid causing duplicate dependencies in projects.
Missing keywords
Help users find your crates. Add
keywords = ["num-format-windows", "windows", "format"]
(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.
argonautica-c
Dependency cbindgen 0.8 is significantly outdated
Upgrade to 0.28.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency itoa 0.4 is significantly outdated
Upgrade to 1.0.15 to get all the fixes, and avoid causing duplicate dependencies in projects.
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"
).
If some of these crates are unmaintained and shouldn't be checked, yank them or add [badges.maintenance]
to their
status = "deprecated"Cargo.toml
.