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.
pulls_since
Dependency clap 2.32 is significantly outdated
Consider upgrading to 4.6.0 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 dotenv 0.13 is significantly outdated
Consider upgrading to 0.15.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 error-chain 0.12 has issues
It may not be actively developed any more. Consider changing the dependency.
Dependency reqwest 0.8 is significantly outdated
Consider upgrading to 0.13.4 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?
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.
skeptic
Dependency error-chain 0.12 has issues
It may not be actively developed any more. Consider changing the dependency.
Buggy README path
The non-local path to readme specified as
\.\./README\.mdexposes a bug in Cargo. Please use a path inside the crate's directory. Symlinks are okay. Please verify the change doesn't break any repo-relative URLs in the README.Dependency cargo_metadata 0.14 is outdated
Upgrade to 0.23.1 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency pulldown-cmark 0.9 is outdated
Upgrade to 0.13.4 to get all the fixes, and avoid causing duplicate dependencies in projects.
Imprecise dependency requirement tempfile = 3
Cargo does not always pick latest versions of dependencies! Specify the version as
tempfile = "3.27.0". IfCargo.lockends 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-versionsflag, 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-versionsCargo option, because it's very easy to accidentally use a feature added in a later version.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").License MIT/Apache-2.0 is not in SPDX syntax
Use
ORinstead of/.README missing from crate tarball
Cargo sometimes fails to package the
READMEfile. Ensure the path to theREADMEinCargo.tomlis 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.