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.
cargo-typesize
Latest stable release is old
It's been over 2 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"
).Nightly crates tend to have a short lifespan. We're delisting them if they're not updated frequently.
Missing keywords
Help users find your crates. Add
keywords = ["cargo", "size", "list", "running", "lib"]
(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.
hermitdb
Dependency git2 0.7.1 is significantly outdated
Upgrade to 0.20.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 ring 0.13.0-alpha is significantly outdated
Upgrade to 0.17.8 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency sled 0.15.17 is significantly outdated
Upgrade to 0.34.7 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency time 0.1.39 is significantly outdated
Upgrade to 0.3.37 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 the crate is truly stable, why not make a 1.0.0 release?
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.
Missing keywords
Help users find your crates. Add
keywords = ["user", "distributed", "log", "distributed-systems", "replicated"]
(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.
cargo-typesize, ctw, hermitdb
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.
cargo-typesize, okasaki, hermitdb, gitdb
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.
gitdb
Dependency git2 0.6.11 is significantly outdated
Upgrade to 0.20.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency ring 0.13.0-alpha is significantly outdated
Upgrade to 0.17.8 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency time 0.1.39 is significantly outdated
Upgrade to 0.3.37 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency toml 0.4.5 is significantly outdated
Upgrade to 0.8.19 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"
).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.
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["cryptography"]
to theCargo.toml
.Missing keywords
Help users find your crates. Add
keywords = ["encrypted", "git", "built", "top", "database"]
(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.Using outdated edition for no reason
We estimate that this crate requires at least Rust 1.54, 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.
ctw
Latest stable release is old
It's been over 2 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"
).
hashseq
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["network-programming"]
to theCargo.toml
.
okasaki
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["data-structures"]
to theCargo.toml
.Missing keywords
Help users find your crates. Add
keywords = ["data-structure", "collection", "peristent"]
(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.
git-db
Crate contains junk files
The crate contains boilerplate Rust files with no real functionality.
If some of these crates are unmaintained and shouldn't be checked, yank them or add [badges.maintenance]
to their
status = "deprecated"Cargo.toml
.