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.
ecfuzz
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.
Failed to verify create's content against its repository
Verified 46 out of 48 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: There is no matching git tag containing version '0.2.4'.
- warning: Had to perform fuzzy search of the head branch due to lack of commit information in the package.
Files in the crates.io crate compared to the repository:
docker-compose.yml
not found.args_from_help.sh
not found.
Fetched
https://github.com/matt24smith/ecfuzz.git
a32bb62a036933265424ed400832c7e1831bff65.Checked on 2024-08-04
This check is experimental.
- warning: The crates.io package has no commit hash associated with it.
Imprecise dependency requirement rayon = 1
Cargo does not always pick latest versions of dependencies! Specify the version as
rayon = "1.10.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 = ["development-tools::testing"]
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 = ["genetic-algorithm", "fuzzing", "coverage", "input", "mutation"]
(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.
mproxy-client
Dependency default-net 0.14 is significantly outdated
Upgrade to 0.22.0 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.
Missing keywords
Help users find your crates. Add
keywords = ["udp-client", "reverse-proxy", "tcp-udp", "udp-server", "proxy-server"]
(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.
mproxy-forward
Dependency rustls 0.20 is outdated
Upgrade to 0.23.23 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency webpki-roots 0.22 is outdated
Upgrade to 0.26.8 to get all the fixes, and avoid causing duplicate dependencies in projects.
Missing keywords
Help users find your crates. Add
keywords = ["tcp-udp", "reverse-proxy", "udp-socket", "networking", "multicast"]
(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.
mproxy-server
Missing keywords
Help users find your crates. Add
keywords = ["udp-server", "reverse-proxy", "tcp-udp", "data-stream", "networking"]
(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.
mproxy-server, mproxy-client, mproxy-reverse, mproxy-forward, mproxy-socket_dispatch
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["network-programming"]
to theCargo.toml
.
mproxy-reverse
Missing keywords
Help users find your crates. Add
keywords = ["reverse-proxy", "proxy-server", "tcp-udp", "networking", "udp-server"]
(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.
mproxy-socket_dispatch
Dependency socket2 0.4 is significantly outdated
Upgrade to 0.5.8 to get all the fixes, and avoid causing duplicate dependencies in projects.
Missing keywords
Help users find your crates. Add
keywords = ["udp-socket", "reverse-proxy", "sockets", "multicast", "networking"]
(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.
No issues found in: mproxy-reverseproxy mproxy-proxy
If some of these crates are unmaintained and shouldn't be checked, yank them or add [badges.maintenance]
to their
status = "deprecated"Cargo.toml
.