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.
xtsn
Dependency hex 0.3.2 is significantly outdated
Upgrade to 0.4.3 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 rust-crypto ^0.2 has issues
It may not be actively developed any more. Consider changing the dependency.
Imprecise dependency requirement byteorder = 1
Cargo does not always pick latest versions of dependencies! Specify the version as
byteorder = "1.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.Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["cryptography"]
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 = ["xtsn", "com-ihaveamac-switchfs", "parser"]
(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.
borrow_trait
License MIT/Apache-2.0 is not in SPDX syntax
Use
OR
instead of/
.
borrow_trait, from_map, shorthand, hashmap_derive
Latest stable release is old
It's been over 5 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"
).
from_map, hashmap_derive, keyguard, safecracker
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.
shorthand
Dependency syn 1.0 is significantly outdated
Upgrade to 2.0.101 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.Incorrect category
Crate's categories property in
Cargo.toml
contains 'procedural macro helpers', which isn't a category we recognizelib.rs has simplified and merged some of crates.io categories. Please file a bug if we got it wrong.
from_map
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["rust-patterns"]
to theCargo.toml
.Missing keywords
Help users find your crates. Add
keywords = ["shorthand", "traits", "proc-macro", "hash-map", "struct"]
(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.
hashmap_derive
Dependency syn 1.0 is significantly outdated
Upgrade to 2.0.101 to get all the fixes, and avoid causing duplicate dependencies in projects.
keyguard
README missing from the repository
We've searched
https://github\.com/luro02/keyguard\.git
and could not find a README file there.Crate is 'reserved'
Please be respectful of crates.io and don't squat crate names.
It's OK if you intend to publish this project in the near future. Keep in mind that even if you have good intentions, things may not go as planned. crates.io won't reclaim abandoned crates, so reserving good names may end up wasting the good names.
safecracker
README missing from the repository
We've searched
https://github\.com/luro02/safecracker\.git
and could not find a README file there.Crate is 'reserved'
Please be respectful of crates.io and don't squat crate names.
If some of these crates are unmaintained and shouldn't be checked, yank them or add [badges.maintenance]
to their
status = "deprecated"Cargo.toml
.