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.
io_self
README missing from the repository
We've searched
https://github\.com/jmeggitt/io\-self\.git
and could not find a README file there.README missing from crate tarball
Cargo sometimes fails to package the
README
file. Ensure the path to theREADME
inCargo.toml
is valid, and points to a file inside the crate's directory.
fmttools
Published crate doesn't match its repository
Partially verified 14 files (includes 2 Cargo-generated).
Fetched
https://github.com/jmeggitt/fmttools.git
8356522084fb19959f33f486576d8502f6ece960.Checked on 2024-08-10
This check is experimental.
Using outdated edition for no reason
We estimate that this crate requires at least Rust 1.63, which is newer than the last 2018-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.
ripeatlas
Dependency itertools 0.10.5 is outdated
Upgrade to 0.14.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.
Dependency ureq 2.5.0 is a bit outdated
Consider upgrading to 3.0.11 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.Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["network-programming"]
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.
gc_api
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["memory-management"]
to theCargo.toml
.
io_self_derive
Buggy README path
The non-local path to readme specified as
\.\./readme\.md
exposes a bug in Cargo. Please use a path inside the crate's directory. Symlinks are okay. Please verify the change doesn't break any repo-relative URLs in the README.README missing from the repository
We've searched
https://github\.com/jmeggitt/io\-self\.git
and could not find a README file there.Dependency darling 0.14 is significantly outdated
Upgrade to 0.20.11 to get all the fixes, and avoid causing duplicate dependencies in projects.
README missing from crate tarball
Cargo sometimes fails to package the
README
file. Ensure the path to theREADME
inCargo.toml
is valid, and points to a file inside the crate's directory.
serde_flat_path, io_self_derive
Dependency syn 1.0 is significantly outdated
Upgrade to 2.0.101 to get all the fixes, and avoid causing duplicate dependencies in projects.
If some of these crates are unmaintained and shouldn't be checked, yank them or add [badges.maintenance]
to their
status = "deprecated"Cargo.toml
.