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.
ico
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["multimedia::images"]
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.
cfb
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["…"]
to theCargo.toml
.Published crate contains binary files
The crate contains binary files (Cab file). 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.
cargo-bundle
Dependency error-chain 0.12 has issues
It may not be actively developed any more. Consider changing the dependency.
Dependency image 0.12 is significantly outdated
Consider upgrading to 0.25.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 target_build_utils 0.3 has issues
It may not be actively developed any more. Consider changing the dependency.
Dependency term 0.4 is significantly outdated
Consider upgrading to 1.0.2 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.Published crate doesn't match its repository
Verified 26 out of 27 files (includes 2 Cargo-generated).
Files in the crates.io crate compared to the repository:
README.md
exists, but elsewhere in the repo.
Fetched
https://github.com/burtonageo/cargo-bundle.git
f91dfdac5c6ff2cbb76154c78e219e4db284d59e.Checked on 2024-08-18
This check is experimental.
Dependency cab 0.4 is outdated
Consider upgrading to 0.6.0 to get all the fixes and improvements.
Dependency cargo_metadata 0.15 is outdated
Consider upgrading to 0.19.2 to get all the fixes and improvements.
Dependency clap ^2 is outdated
Consider upgrading to 4.5.38 to get all the fixes and improvements.
Dependency dirs 1.0 is outdated
Consider upgrading to 6.0.0 to get all the fixes and improvements.
Dependency libflate 1.2 is outdated
Consider upgrading to 2.1.0 to get all the fixes and improvements.
Dependency msi 0.6 is outdated
Consider upgrading to 0.8.0 to get all the fixes and improvements.
Dependency strsim 0.10 is outdated
Consider upgrading to 0.11.1 to get all the fixes and improvements.
Dependency toml 0.5 is outdated
Consider upgrading to 0.8.22 to get all the fixes and improvements.
Imprecise dependency requirement clap = ^2
Cargo does not always pick latest versions of dependencies! Specify the version as
clap = "4.5.38"
. IfCargo.lock
ends up having an unexpectedly old version of the dependency, you might get a dependency that lacks features/APIs or important bugfixes that you depend on. This is most likely to happen when using theminimal-versions
flag, used by users of old Rust versions.If you want to keep using truly minimal dependency requirements, please make sure you test them in CI with
-Z minimal-versions
Cargo option, because it's very easy to accidentally use a feature added in a later version.Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["development-tools::cargo-plugins"]
to theCargo.toml
.
icns
Dependency png 0.16 is significantly outdated
Upgrade to 0.17.16 to get all the fixes, and avoid causing duplicate dependencies in projects.
Latest stable release is old
It's been over 4 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?
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["multimedia::images"]
to theCargo.toml
.Using outdated edition for no reason
We estimate that this crate requires at least Rust 1.45, 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.
ar
Latest stable release is old
It's been over 3 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"
).Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["compression"]
to theCargo.toml
.
ico, cfb, msi, cab, icns
Imprecise dependency requirement byteorder = 1
Cargo does not always pick latest versions of dependencies! Specify the version as
byteorder = "1.5.0"
. IfCargo.lock
ends up having an unexpectedly old version of the dependency, you might get a dependency that lacks features/APIs or important bugfixes that you depend on. This is most likely to happen when using theminimal-versions
flag, used by users of old Rust versions.
cab
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["compression"]
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
.