Lib.rs

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.

• public-ip

  • Dependency trust-dns-client 0.20 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.

    trust-dns-client crate

  • Dependency trust-dns-proto 0.20 is significantly outdated

    Upgrade to 0.23.2 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.

    trust-dns-proto versions

  • Imprecise dependency requirement thiserror = 1

    Cargo does not always pick latest versions of dependencies! Specify the version as thiserror = "2.0.12". If Cargo.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 the minimal-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.

    thiserror versions

  • Dependency dns-lookup 1 is outdated

    Upgrade to 2.0.4 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.

    dns-lookup versions

  • Dependency http 0.2 is outdated

    Upgrade to 1.3.0 to get all the fixes, and avoid causing duplicate dependencies in projects.

    http versions

  • Dependency hyper 0.14 is outdated

    Upgrade to 1.6.0 to get all the fixes, and avoid causing duplicate dependencies in projects.

    hyper versions

  • Dependency thiserror 1 is a bit outdated

    Consider upgrading to 2.0.12 to get all the fixes and improvements.

    thiserror versions

• public-ip, dangerous, aliasable_deref_trait

  • 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").

    If the crate is truly stable, why not make a 1.0.0 release?

    Maintenance status field docs

• feast

  • Latest stable release is old

    It's been over 5 years. How did the experiment go? Make a new release, either to refresh it, or to set

    [badges.maintenance]
    status = "deprecated"
    

    (or "as-is", "passively-maintained").

    Maintenance status field docs

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["…"] to the Cargo.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.

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["byte", "feast", "parser"] (up to 5) to the Cargo.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.

• mdbook-tera

  • Dependency clap ~3 is significantly outdated

    Upgrade to 4.5.37 to get all the fixes, and avoid causing duplicate dependencies in projects.

    clap versions

  • Dependency globwalk 0.8 is significantly outdated

    Upgrade to 0.9.1 to get all the fixes, and avoid causing duplicate dependencies in projects.

    globwalk versions

  • Imprecise dependency requirement anyhow = ~1

    Cargo does not always pick latest versions of dependencies! Specify the version as anyhow = "1.0.98". If Cargo.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 the minimal-versions flag, used by users of old Rust versions.

    anyhow versions

  • Dependency toml ~0.5 is outdated

    Upgrade to 0.8.22 to get all the fixes, and avoid causing duplicate dependencies in projects.

    toml versions

• owning_ref

  • Reported security advisory RUSTSEC-2022-0040

    Multiple soundness issues in `owning_ref`

    All crate audits

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["concurrency"] to the Cargo.toml.

    List of available categories

• dangerous

  • Dependency nom 6 is significantly outdated

    Upgrade to 8.0.0 to get all the fixes, and avoid causing duplicate dependencies in projects.

    nom versions

  • Dependency unicode-width 0.1 is a bit outdated

    Consider upgrading to 0.2.0 to get all the fixes and improvements.

    unicode-width versions

• aliasable

  • Dependency aliasable_deref_trait 0.2 is slightly outdated

    Consider upgrading to 1.0.0 to get all the fixes and improvements.

    aliasable_deref_trait versions

  • Missing keywords

    Help users find your crates. Add keywords = ["aliasable", "type", "why", "language", "noalias"] (up to 5) to the Cargo.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.

• badgen

  • Dependency itoa 0.4 is significantly outdated

    Upgrade to 1.0.15 to get all the fixes, and avoid causing duplicate dependencies in projects.

    itoa versions

  • Dependency ttf-parser 0.8 is significantly outdated

    Upgrade to 0.25.1 to get all the fixes, and avoid causing duplicate dependencies in projects.

    ttf-parser versions

  • Dependency uluru 1 is significantly outdated

    Upgrade to 3.1.0 to get all the fixes, and avoid causing duplicate dependencies in projects.

    uluru versions

  • Imprecise dependency requirement uluru = 1

    Cargo does not always pick latest versions of dependencies! Specify the version as uluru = "3.1.0". If Cargo.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 the minimal-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.

    uluru versions

  • Missing keywords

    Help users find your crates. Add keywords = ["graphics", "generator", "badgen", "classic", "badge-generator"] (up to 5) to the Cargo.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.

• abuseipdb

  • Dependency reqwest 0.10 is significantly outdated

    Upgrade to 0.12.15 to get all the fixes, and avoid causing duplicate dependencies in projects.

    reqwest versions

  • Dependency serde_urlencoded 0.6 is significantly outdated

    Upgrade to 0.7.1 to get all the fixes, and avoid causing duplicate dependencies in projects.

    serde_urlencoded versions

  • Imprecise dependency requirement serde = ~1

    Cargo does not always pick latest versions of dependencies! Specify the version as serde = "1.0.219". If Cargo.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 the minimal-versions flag, used by users of old Rust versions.

    serde versions

  • Dependency jsonapi 0.6 is slightly outdated

    Consider upgrading to 0.7.0 to get all the fixes and improvements.

    jsonapi versions

  • Missing keywords

    Help users find your crates. Add keywords = ["client", "api-bindings", "abuseipdb", "ipv4-addr", "async"] (up to 5) to the Cargo.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.

• dnscat

  • Dependency structopt ~0.3 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.

    structopt crate

  • Dependency trust-dns-client ~0.19 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.

    trust-dns-client crate

  • Dependency bitflags ~1.2 is significantly outdated

    Upgrade to 2.9.0 to get all the fixes, and avoid causing duplicate dependencies in projects.

    bitflags versions

  • Dependency bytes ~0.5 is significantly outdated

    Upgrade to 1.10.0 to get all the fixes, and avoid causing duplicate dependencies in projects.

    bytes versions

  • Dependency failure ~0.1 has issues

    It may not be actively developed any more. Consider changing the dependency.

    failure crate

  • Dependency generic-array ~0.12 is significantly outdated

    Upgrade to 1.2.0 to get all the fixes, and avoid causing duplicate dependencies in projects.

    generic-array versions

  • Dependency itertools ~0.9 is significantly outdated

    Upgrade to 0.14.0 to get all the fixes, and avoid causing duplicate dependencies in projects.

    itertools versions

  • Dependency rand ~0.7 is significantly outdated

    Upgrade to 0.9.1 to get all the fixes, and avoid causing duplicate dependencies in projects.

    rand versions

  • Dependency salsa20 0.4 is significantly outdated

    Upgrade to 0.10.2 to get all the fixes, and avoid causing duplicate dependencies in projects.

    salsa20 versions

  • Dependency sha3 0.8 is significantly outdated

    Upgrade to 0.10.8 to get all the fixes, and avoid causing duplicate dependencies in projects.

    sha3 versions

  • Dependency tokio ~0.2 has issues

    It may not be actively developed any more. Consider changing the dependency.

    tokio crate

  • Dependency constant_time_eq 0.1 is significantly outdated

    Upgrade to 0.4.2 to get all the fixes, and avoid causing duplicate dependencies in projects.

    constant_time_eq versions

  • Dependency env_logger ~0.7 is outdated

    Upgrade to 0.11.8 to get all the fixes, and avoid causing duplicate dependencies in projects.

    env_logger versions

  • Dependency ring 0.16 is outdated

    Upgrade to 0.17.14 to get all the fixes, and avoid causing duplicate dependencies in projects.

    ring versions

  • Dependency secstr 0.4 is outdated

    Upgrade to 0.5.1 to get all the fixes, and avoid causing duplicate dependencies in projects.

    secstr versions

  • Dependency trust-dns-proto ~0.19 is outdated

    Upgrade to 0.23.2 to get all the fixes, and avoid causing duplicate dependencies in projects.

    trust-dns-proto versions

  • Dependency trust-dns-resolver ~0.19 is outdated

    Upgrade to 0.23.2 to get all the fixes, and avoid causing duplicate dependencies in projects.

    trust-dns-resolver versions

  • Missing keywords

    Help users find your crates. Add keywords = ["protocols", "dnscat", "block", "language", "dnscat2"] (up to 5) to the Cargo.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.

• aliasable, zc, badgen, zc-derive

  • 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").

    Maintenance status field docs

• liptk

  • 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").

    Maintenance status field docs

  • 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.

    More info

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["cryptography"] to the Cargo.toml.

    List of available categories

• owning_ref, arae, abuseipdb, dnscat, dnscat-client

  • 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").

    Maintenance status field docs

• arae

  • Dependency loom 0.2 is significantly outdated

    Upgrade to 0.7.2 to get all the fixes, and avoid causing duplicate dependencies in projects.

    loom versions

  • Missing keywords

    Help users find your crates. Add keywords = ["structures", "bounded", "element", "cursor"] (up to 5) to the Cargo.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.

• dnscat-client

  • Dependency tokio 0.2 has issues

    It may not be actively developed any more. Consider changing the dependency.

    tokio crate

  • Missing keywords

    Help users find your crates. Add keywords = ["client", "dnscat", "dnscat-client"] (up to 5) to the Cargo.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.

• liptk, dnscat-client, zc-derive, dnscat-server, sk, oskt

  • README missing from crate tarball

    Cargo sometimes fails to package the README file. Ensure the path to the README in Cargo.toml is valid, and points to a file inside the crate's directory.

• zc-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.

    syn versions

• dnscat-server, nxu

  • Crate contains junk files

    The crate contains boilerplate Rust files with no real functionality.

• sk

  • 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.

• oskt

  • 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]
status = "deprecated" to their Cargo.toml.