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.
tracing-callgraph
Latest prerelease 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"
).Users pay attention to the latest release date. Even if the crate is perfectly fine as-is, users may not know that.
Dependency petgraph 0.5.1 is significantly outdated
Upgrade to 0.8.1 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 tracing-subscriber 0.2.10 is significantly outdated
Upgrade to 0.3.19 to get all the fixes, and avoid causing duplicate dependencies in projects.
Published crate doesn't match its repository
Partially verified 10 files (includes 3 Cargo-generated).
Files in the crates.io crate compared to the repository:
Cargo.lock
not found.
Fetched
https://github.com/hlb8122/tracing-callgraph.git
0b9b4e04740df6ea363473d5e7b671e2e6512fdd.Checked on 2024-08-10
This check is experimental.
bevy_stokes
Latest prerelease 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"
).Dependency bevy 0.6.1 is significantly outdated
Upgrade to 0.16.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Published crate doesn't match its repository
Partially verified 11 files (includes 3 Cargo-generated).
Files in the crates.io crate compared to the repository:
Cargo.lock
not found.
Fetched
https://github.com/hlb8122/bevy_stokes.git
d73c47272fe7c26dc921b15f7ff4ea589bf27c73.Checked on 2024-07-28
async-json-rpc
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["…"]
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.
Dependency base64 0.13.0 is outdated
Upgrade to 0.22.1 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency hyper 0.14.2 is outdated
Upgrade to 1.6.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Easy way to bump dependencies:
cargo install cargo-edit; cargo upgrade -i
; Also check out Dependabot service on GitHub.Dependency hyper-tls 0.5.0 is outdated
Upgrade to 0.6.0 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?
cashweb-secp256k1, cashweb, bitcoincash-addr, bitcoin-zmq, cashweb-bitcoin, cashweb-keyserver-client, cashweb-bitcoin-client, cashweb-relay-client, cashweb-token, cashweb-relay, cashweb-payments, cashweb-auth-wrapper, cashweb-keyserver
Cryptocurrency crate
This crate has been classified as related to cyrptocurrencies. If you believe this categorization is a mistake, then please review crate's categories and keywords, or file a bug. If it is related, then please reconsider your choices, and yank it.
Author of this site is firmly convinced that cryptocurrencies have a net-negative effect on society.
cashweb-secp256k1-sys
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"
).Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["cryptography"]
to theCargo.toml
.Published crate contains binary files
The crate contains binary files (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.
No issues found in: cashweb-protobuf
If some of these crates are unmaintained and shouldn't be checked, yank them or add [badges.maintenance]
to their
status = "deprecated"Cargo.toml
.