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.
ls_solver
Published crate doesn't match its repository
Partially verified 131 files (includes 2 Cargo-generated).
Fetched
https://github.com/dcmonti/ls_solver.git
2cac064216fb1a03215c504a16b5bf2976384b07.Checked on 2024-07-28
This check is experimental.
Dependency nalgebra 0.32.2 is outdated
Upgrade to 0.33.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 nalgebra-sparse 0.9.0 is outdated
Upgrade to 0.10.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["mathematics"]
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.
Published crate contains binary files
The crate contains binary files (WOFF font). Crates are meant to be compiled from source. Please check that you haven't published temporary build files by accident. If you have test fixtures, consider excluding them from crates-io tarball, since Cargo doesn't run tests from crates-io packages.
If some of these crates are unmaintained and shouldn't be checked, yank them or add [badges.maintenance]
to their
status = "deprecated"Cargo.toml
.