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.
fixed
Imprecise dependency requirement arbitrary = 1
Cargo does not always pick latest versions of dependencies! Specify the version as
arbitrary = "1.4.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.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.
rox
Failed to verify create's content against its repository
Could not check any files
- warning: The crates.io package has no information about its path inside its repository.
- error: Repository doesn't exist: Can't checkout the repository. It's either gone or private: remote authentication required but no callback set; class=Http (34); code=Auth (-16).
- Make sure the
repository
URL inCargo.toml
is correct and works withgit clone
. The repository must be public.
- Make sure the
Checked on 2025-02-16
This check is experimental.
Dependency clap 2 is outdated
Consider upgrading to 4.5.37 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.Imprecise dependency requirement clap = 2
Cargo does not always pick latest versions of dependencies! Specify the version as
clap = "4.5.37"
. 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.
rug
docs.rs build failed
docs.rs site failed to build the crate, so users will have trouble finding the documentation. Docs.rs supports multiple platforms and custom configurations, so you can make the build work even if normal crate usage has special requirements.
Docs.rs doesn't need to run or even link any code, so system dependencies can simply be skipped. You can also set
cfg()
flags just for docs.rs and use them to hide problematic code.
gmp-mpfr-sys
Published crate contains binary files
The crate contains binary files (autotools obfuscated code, obscure autoconf code). 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.
crox
Crate contains junk files
The crate contains boilerplate Rust files with no real functionality.
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.
bree
Crate contains junk files
The crate contains boilerplate Rust files with no real functionality.
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.
rugcom
Internal error
We couldn't check this crate at this time, because: Crate needed for the dashboard Origin( lib.rs/crates/rugcom ). Please try again later.
scat
Internal error
We couldn't check this crate at this time, because: Crate needed for the dashboard Origin( lib.rs/crates/scat ). Please try again later.
No issues found in: rugflo rugrat rugint gmp-mpfr
If some of these crates are unmaintained and shouldn't be checked, yank them or add [badges.maintenance]
to their
status = "deprecated"Cargo.toml
.