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.
webauthn-rs
Imprecise dependency requirement url = 2
Cargo does not always pick latest versions of dependencies! Specify the version as
url = "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.
tunnelto
Dependency structopt 0.3.12 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 askama 0.9.0 is significantly outdated
Upgrade to 0.12.1 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 colored 1.9.3 is significantly outdated
Upgrade to 3.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.Dependency dirs 2.0.2 is significantly outdated
Upgrade to 6.0.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency http-body 0.3.1 is significantly outdated
Upgrade to 1.0.1 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency hyper-rustls 0.22.1 is significantly outdated
Upgrade to 0.27.5 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency indicatif 0.15.0 is significantly outdated
Upgrade to 0.17.11 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency semver 0.11 is significantly outdated
Upgrade to 1.0.25 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency serde_urlencoded 0.6.1 is significantly outdated
Upgrade to 0.7.1 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency tokio-rustls 0.22 is significantly outdated
Upgrade to 0.26.1 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency tokio-tungstenite 0.14 is significantly outdated
Upgrade to 0.26.1 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency tungstenite 0.13 is significantly outdated
Upgrade to 0.26.1 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency uuid 0.8.1 is significantly outdated
Upgrade to 1.12.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency webpki-roots 0.21 is significantly outdated
Upgrade to 0.26.8 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency human-panic 1.0.3 is outdated
Consider upgrading to 2.0.2 to get all the fixes and improvements.
Dependency hyper 0.14 is outdated
Upgrade to 1.6.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency pretty_env_logger 0.4.0 is outdated
Upgrade to 0.5.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency reqwest 0.11 is outdated
Upgrade to 0.12.12 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency thiserror 1.0 is a bit outdated
Consider upgrading to 2.0.11 to get all the fixes and improvements.
Failed to verify create's content against its repository
Verified 18 out of 23 files (includes 3 Cargo-generated).
- warning: Crate tarball has been published from the commit bb2104e45abec8e13e3e8c54883427888386d74d, which is not in the repository.
- Create git tags after comitting any changes, and commit changes after bumping versions and running
cargo update
.
- Create git tags after comitting any changes, and commit changes after bumping versions and running
- warning: Found a Cargo.toml for this package in its repo (via tags), but the version was different.
- Make sure to commit and tag after bumping the version number.
- warning: Had to perform fuzzy search of the head branch due to lack of commit information in the package.
- error: Manifest properties don't match: Existence of [lib] inconsistent: published=true; orig=false.
Files in the crates.io crate compared to the repository:
Cargo.lock
not found.README.md
does not match the repository.Cargo.toml.orig
does not match the repository.src/
main.rs
does not match the repository.lib.rs
not found.
mod.rs
does not match the repository.
Looked for the crate in
tunnelto/
. Fetchedhttps://github.com/agrinman/tunnelto.git
8e0957dc569b84f2f14fe91848afc81f7a98324f.Checked on 2024-10-23
This check is experimental.
- warning: Crate tarball has been published from the commit bb2104e45abec8e13e3e8c54883427888386d74d, which is not in the repository.
Missing keywords
Help users find your crates. Add
keywords = ["web-server", "local-server", "url", "expose", "async-io"]
(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.
tunnelto_protocol
Failed to verify create's content against its repository
Verified 1 out of 4 files (includes 1 Cargo-generated).
- warning: The crates.io package has no commit hash associated with it.
- Publish a new version, without using
--allow-dirty
flag. Make sure all changes are committed before publishing. Useinclude
/exclude
inCargo.toml
to omit unnecessary files.
- Publish a new version, without using
- warning: The crates.io package has no information about its path inside its repository.
- warning: Could not discover crate's location in its repository (via tags).
- warning: Could not find any matching commit in the repository. Used latest commit as a fallback. The results may be incorrect.
- warning: There is no matching git tag containing version '0.1.20'.
- warning: Had to perform fuzzy search of the head branch due to lack of commit information in the package.
- error: Manifest properties don't match: Existence of [lib] inconsistent: published=true; orig=false.
Files in the crates.io crate compared to the repository:
README.md
does not match the repository.Cargo.toml.orig
does not match the repository.lib.rs
not found.
Fetched
https://github.com/agrinman/tunnelto.git
06428f13c638180dd349a4c42a17b569ab51a25f.Checked on 2024-10-23
- warning: The crates.io package has no commit hash associated with it.
Dependency sha2 0.9.1 is significantly outdated
Upgrade to 0.10.8 to get all the fixes, and avoid causing duplicate dependencies in projects.
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.
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["web-programming"]
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 = ["web-server", "expose", "public", "url", "local"]
(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.
wormhole-tunnel
Dependency structopt 0.3.12 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 bytes 0.5.4 is significantly outdated
Upgrade to 1.10.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency dirs 2.0.2 is significantly outdated
Upgrade to 6.0.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency hmac-sha256 0.1.2 is significantly outdated
Upgrade to 1.1.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency tokio 0.2 has issues
It may not be actively developed any more. Consider changing the dependency.
Dependency tokio-tungstenite 0.10.1 is significantly outdated
Upgrade to 0.26.1 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency tungstenite 0.10.1 is significantly outdated
Upgrade to 0.26.1 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency warp 0.2.2 is significantly outdated
Upgrade to 0.3.7 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency colour 0.5.0 is outdated
Upgrade to 2.1.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency human-panic 1.0.3 is outdated
Consider upgrading to 2.0.2 to get all the fixes and improvements.
Dependency pretty_env_logger 0.4.0 is outdated
Upgrade to 0.5.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
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 = ["web-server", "local", "url", "expose", "wormhole"]
(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.
tunnelto_lib
Dependency sha2 0.9.1 is significantly outdated
Upgrade to 0.10.8 to get all the fixes, and avoid causing duplicate dependencies in projects.
Buggy README path
The non-local path to readme specified as
\.\./README\.md
exposes 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.Latest stable release is old
It's been over 3 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"
).Missing keywords
Help users find your crates. Add
keywords = ["server", "tunnelto", "expose", "public", "local"]
(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.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.
tunnelto_protocol, wormhole-tunnel, tunnelto_lib
Dependency base64 0.11.0 is significantly outdated
Upgrade to 0.22.1 to get all the fixes, and avoid causing duplicate dependencies in projects.
tunnelto_protocol, wormhole-tunnel, tunnelto_lib
Dependency rand 0.7.3 is significantly outdated
Upgrade to 0.9.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
tunnelto, wormhole-tunnel, tunnelto_lib
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["web-programming::http-server"]
to theCargo.toml
.
base-62
Dependency failure 0.1.5 has issues
It may not be actively developed any more. Consider changing the dependency.
Dependency num-bigint 0.2.2 is significantly outdated
Upgrade to 0.4.6 to get all the fixes, and avoid causing duplicate dependencies in projects.
Latest stable release is old
It's been over 6 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"
).Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["encoding"]
to theCargo.toml
.
If some of these crates are unmaintained and shouldn't be checked, yank them or add [badges.maintenance]
to their
status = "deprecated"Cargo.toml
.