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.
aws-sg-cleanup
Dependency aws-config 0.15.0 is significantly outdated
Consider upgrading to 1.5.18 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.Dependency aws-sdk-ec2 0.15.0 is significantly outdated
Consider upgrading to 1.116.0 to get all the fixes and improvements.
Dependency aws-sdk-lambda 0.15.0 is significantly outdated
Consider upgrading to 1.71.0 to get all the fixes and improvements.
Dependency aws-types 0.15.0 is significantly outdated
Consider upgrading to 1.3.0 to get all the fixes and improvements.
Dependency base16ct 0.1.1 is significantly outdated
Consider upgrading to 0.2.0 to get all the fixes and improvements.
In Cargo, different 0.x versions are considered incompatible, so this is a semver-major upgrade.
Dependency clap 3.2.12 is significantly outdated
Consider upgrading to 4.5.31 to get all the fixes and improvements.
Dependency sha-1 0.10.0 has issues
It may not be actively developed any more. Consider changing the dependency.
Dependency aws-sdk-elasticache 0.15.0 is outdated
Consider upgrading to 1.66.0 to get all the fixes and improvements.
Dependency aws-sdk-elasticloadbalancingv2 0.15.0 is outdated
Consider upgrading to 1.70.0 to get all the fixes and improvements.
Dependency aws-sdk-rds 0.15.0 is outdated
Consider upgrading to 1.80.0 to get all the fixes and improvements.
Dependency env_logger 0.9.0 is outdated
Consider upgrading to 0.11.6 to get all the fixes and improvements.
Dependency itertools 0.10.3 is outdated
Consider upgrading to 0.14.0 to get all the fixes and improvements.
Dependency rand 0.8.5 is a bit outdated
Consider upgrading to 0.9.0 to get all the fixes and improvements.
cargo-dock
README missing from the repository
We've searched
https://github\.com/barbuza/cargo\-dock\.git
and could not find a README file there.Dependency toml 0.4.2 is significantly outdated
Consider upgrading to 0.8.20 to get all the fixes and improvements.
Latest stable release is old
It's been over 7 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?
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.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.
Dependency clap 2.25.1 is outdated
Consider upgrading to 4.5.31 to get all the fixes and improvements.
Dependency rustc_version 0.2.1 is outdated
Consider upgrading to 0.4.1 to get all the fixes and improvements.
Dependency unindent 0.1.0 is outdated
Consider upgrading to 0.2.4 to get all the fixes and improvements.
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["development-tools::cargo-plugins"]
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 = ["docker-build", "docker", "build", "dead-simple"]
(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
.