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.
snapshotfs
Dependency fuser 0.12 is significantly outdated
Consider upgrading to 0.15.1 to get all the fixes and improvements.
In Cargo, different 0.x versions are considered incompatible, so this is a semver-major upgrade.
Dependency env_logger 0.9 is outdated
Consider upgrading to 0.11.6 to get all the fixes and improvements.
Imprecise dependency requirement walkdir = 2
Cargo does not always pick latest versions of dependencies! Specify the version as
walkdir = "2.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.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.
transformfs
Imprecise dependency requirement anyhow = 1
Cargo does not always pick latest versions of dependencies! Specify the version as
anyhow = "1.0.95"
. 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.This crate does not bump semver-minor when adding new features, so to be safe you get all the features/APIs/fixes that your crate depends on, require a more specific patch version.
Dependency fuser 0.14 is outdated
Consider upgrading to 0.15.1 to get all the fixes and improvements.
rangefs
Dependency itertools 0.12 is significantly outdated
Consider upgrading to 0.14.0 to get all the fixes and improvements.
Dependency env_logger 0.9 is outdated
Consider upgrading to 0.11.6 to get all the fixes and improvements.
Dependency fuser 0.14 is outdated
Consider upgrading to 0.15.1 to get all the fixes and improvements.
chord-dht
Dependency clap 3.1 is significantly outdated
Upgrade to 4.5.28 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 inquire 0.3.0-alpha.2 is significantly outdated
Upgrade to 0.7.5 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency tarpc 0.27 is significantly outdated
Upgrade to 0.35.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency env_logger 0.9 is outdated
Upgrade to 0.11.6 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency rand 0.8 is a bit outdated
Consider upgrading to 0.9.0 to get all the fixes and improvements.
Dependency thiserror 1.0 is a bit outdated
Consider upgrading to 2.0.11 to get all the fixes and improvements.
Imprecise dependency requirement tokio = 1
Cargo does not always pick latest versions of dependencies! Specify the version as
tokio = "1.43.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.
secret-sharing-cli
Dependency base64 0.12 is significantly outdated
Consider upgrading to 0.22.1 to get all the fixes and improvements.
Dependency clap ^2.33.1 is outdated
Consider upgrading to 4.5.28 to get all the fixes and improvements.
Dependency sharks 0.4 is outdated
Consider upgrading to 0.5.0 to get all the fixes and improvements.
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 keywords
Help users find your crates. Add
keywords = ["secret-sharing", "shamir-secret-sharing"]
(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.
If some of these crates are unmaintained and shouldn't be checked, yank them or add [badges.maintenance]
to their
status = "deprecated"Cargo.toml
.