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.
k8s-openapi, k8s-openapi-codegen-common
Imprecise dependency requirement serde = 1
Cargo does not always pick latest versions of dependencies! Specify the version as
serde = "1.0.219"
. 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.
k8s-openapi-derive
Imprecise dependency requirement syn = 2
Cargo does not always pick latest versions of dependencies! Specify the version as
syn = "2.0.100"
. 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.
uapi-config
Dependency dirs 5 is outdated
Upgrade to 6.0.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.
derive-error-chain
Dependency syntex_fmt_macros 0.5.x has issues
It has been losing active users, which may be a sign it's deprecated or obsolete. Consider replacing it with a different crate.
Dependency proc-macro2 0.4.x is significantly outdated
Upgrade to 1.0.94 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency quote 0.6.x is significantly outdated
Upgrade to 1.0.40 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency syn 0.14.x is significantly outdated
Upgrade to 2.0.100 to get all the fixes, and avoid causing duplicate dependencies in projects.
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.
License MIT/Apache-2.0 is not in SPDX syntax
Use
OR
instead of/
.
If some of these crates are unmaintained and shouldn't be checked, yank them or add [badges.maintenance]
to their
status = "deprecated"Cargo.toml
.