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.
rmtg_server
No repository property
Specify git repository URL in
Cargo.toml
to help users find more information, contribute, and for lib.rs to read more info.The Cargo package has no git commit information
Before publishing a package, make sure all packaged files are committed to the repository, and there are no "dirty" files. Push this commit to crate's public repository.
To protect against supply chain attacks similar to CVE-2024-3094, lib.rs will soon start flagging non-reproducible packages without public source code as suspicious. Currently only git repositories are supported (but may be hosted anywhere, not just GitHub). If you'd like a different SCM supported, please file a feature request.
Imprecise dependency requirement tokio = 1
Cargo does not always pick latest versions of dependencies! Specify the version as
tokio = "1.44.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.Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["development-tools"]
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.
Missing keywords
Help users find your crates. Add
keywords = ["mtg", "server", "rmtg", "name", "git"]
(up to 5) to theCargo.toml
. Best keywords are alternative terms or their spellings that aren't in the name or description. Also add a keyword that precisely categorizes this crate and groups it with other similar crates.
rmtg_core
No repository property
Specify git repository URL in
Cargo.toml
to help users find more information, contribute, and for lib.rs to read more info.The Cargo package has no git commit information
Before publishing a package, make sure all packaged files are committed to the repository, and there are no "dirty" files. Push this commit to crate's public repository.
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["development-tools"]
to theCargo.toml
.Missing keywords
Help users find your crates. Add
keywords = ["mtg", "git", "gitlab", "git-repository", "git-remote"]
(up to 5) to theCargo.toml
. Best keywords are alternative terms or their spellings that aren't in the name or description. Also add a keyword that precisely categorizes this crate and groups it with other similar crates.Using outdated edition for no reason
We estimate that this crate requires at least Rust 1.51, 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.
bitvavo-client
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.
If some of these crates are unmaintained and shouldn't be checked, yank them or add [badges.maintenance]
to their
status = "deprecated"Cargo.toml
.