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.
graylog-to-grafana
Dependency structopt 0.2 has issues
It has been losing active users, which may be a sign it's deprecated or obsolete. Consider replacing it with a different crate.
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 env_logger 0.6 is significantly outdated
Consider upgrading to 0.11.6 to get all the fixes and improvements.
In Cargo, different 0.x versions are considered incompatible, so this is a semver-major upgrade.
Dependency reqwest 0.9 is significantly outdated
Consider upgrading to 0.12.12 to get all the fixes and improvements.
Dependency url 1.7.2 is significantly outdated
Consider upgrading to 2.5.0 to get all the fixes and improvements.
Easy way to bump dependencies:
cargo install cargo-edit; cargo upgrade -i
; Also check out Dependabot service on GitHub.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?
dust
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"
).Nightly crates tend to have a short lifespan. We're delisting them if they're not updated frequently.
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["…"]
to theCargo.toml
.Dependency proc-macro2 0.2 is significantly outdated
Upgrade to 1.0.94 to get all the fixes, and avoid causing duplicate dependencies in projects.
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 = ["data-driven", "testing", "build"]
(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.
vorbisenc-sys
Internal error
We couldn't check this crate at this time, because: deadline has elapsed. Please try again later.
If some of these crates are unmaintained and shouldn't be checked, yank them or add [badges.maintenance]
to their
status = "deprecated"Cargo.toml
.