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.
redis_rocksdb
Published crate doesn't match its repository
Partially verified 52 files (includes 2 Cargo-generated).
Fetched
https://github.com/peacess/redis_rocksdb.git
74a60d914a40e512d6e68539db081e5441950198.Checked on 2024-08-10
This check is experimental.
Dependency rocksdb 0.22.0 is outdated
Upgrade to 0.23.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.
db_code
Published crate doesn't match its repository
Partially verified 10 files (includes 3 Cargo-generated).
Files in the crates.io crate compared to the repository:
Cargo.lock
does not match the repository.
Looked for the crate in
code/
. Fetchedhttps://github.com/peacess/db_code.git
d574fd588b1bb7840a7596252c8c5ae991c3f3f8.Checked on 2025-04-06
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["database"]
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.
No issues found in: lite_db db_code_macro door_player rust_kits
If some of these crates are unmaintained and shouldn't be checked, yank them or add [badges.maintenance]
to their
status = "deprecated"Cargo.toml
.