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.
minimax
Dependency instant 0.1 has issues
It may not be actively developed any more. Consider changing the dependency.
Published crate doesn't match its repository
Partially verified 27 files (includes 3 Cargo-generated).
Files in the crates.io crate compared to the repository:
Cargo.lock
not found.
Fetched
https://github.com/edre/minimax-rs.git
1c094fdae8123408fcd8f6f726ef5d419245df50.Checked on 2025-02-23
This check is experimental.
Dependency getrandom 0.2 is outdated
Upgrade to 0.3.2 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 rand 0.8 is a bit outdated
Consider upgrading to 0.9.1 to get all the fixes and improvements.
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["game-development"]
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.
deque
Latest stable release is old
It's been over 8 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.
License Apache-2.0/MIT is not in SPDX syntax
Use
OR
instead of/
.Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["concurrency"]
to theCargo.toml
.
async-local-bounded-channel
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["…"]
to theCargo.toml
.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.Dependency generic-array 0.13 is significantly outdated
Upgrade to 1.2.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.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"
).
shawshank
Dependency num-traits 0.1 is significantly outdated
Upgrade to 0.2.19 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.
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["rust-patterns"]
to theCargo.toml
.
If some of these crates are unmaintained and shouldn't be checked, yank them or add [badges.maintenance]
to their
status = "deprecated"Cargo.toml
.