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.

• smex

  • Failed to verify create's content against its repository

    Verified 7 out of 9 files (includes 3 Cargo-generated).

    • warning: Crate tarball has been published from the commit 6b05e48c3e477977e81fb5ab7dab56c6f2d8acad, which is not in the repository.
      • Create git tags after comitting any changes, and commit changes after bumping versions and running cargo update.
    • 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.

    Files in the crates.io crate compared to the repository:

    • Cargo.lock does not match the repository.
    • Cargo.toml.orig does not match the repository.
    • lib.rs does not match the repository.

    Fetched https://git.distrust.co/public/smex e3133ae8e6a83769ddbf01566d1e5bd5aa185c3c.

    Checked on 2026-03-29

    This check is experimental.

    Forum thread

  • README missing from the repository

    We've searched https://git\.distrust\.co/public/smex and could not find a README file there.

  • No readme property

    Specify path to a README file for the project, so that information about is included in the crates.io tarball.

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["encoding"] 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 = ["encoding-decoding", "zero-dependency", "hex-encoding", "decode", "string"] (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.

• dterror

  • README missing from the repository

    We've searched https://git\.distrust\.co/public/dterror and could not find a README file there.

  • No readme property

    Specify path to a README file for the project, so that information about is included in the crates.io tarball.

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["dat", "error-handling", "context", "long-lived"] (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.

• blahaj

  • Dependency arbitrary 0.4.7 is significantly outdated

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

    arbitrary versions

  • Dependency hashbrown 0.15 is significantly outdated

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

    hashbrown versions

  • Published crate doesn't match its repository

    Partially verified 14 files (includes 2 Cargo-generated).

    Fetched https://git.distrust.co/public/blahaj fc517a8047bb1ddb8f5df8b34cab3214e5aec338.

    Checked on 2024-11-17

    Forum thread

  • Dependency rand 0.8 is outdated

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

    rand versions

  • Optional dependency 'arbitrary' exposed as an implicit feature

    Cargo automatically makes publicly-available crate features for every optional dependency, unless the dependencies are referenced using dep: syntax. Features 'arbitrary', 'zeroize' may have been unintentional.

    Crate features

• k8s-ares

  • No repository property

    Specify git repository URL in Cargo.toml to help users find more information, contribute, and for lib.rs to read more info.

  • Dependency clap 3.0.0-beta.1 is significantly outdated

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

    clap versions

  • Dependency k8s-openapi 0.9.0 is significantly outdated

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

    k8s-openapi versions

  • Dependency kube 0.40.0 is significantly outdated

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

    kube versions

  • Dependency kube-derive 0.40.0 is significantly outdated

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

    kube-derive versions

  • Dependency kube-runtime 0.40.0 is significantly outdated

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

    kube-runtime versions

  • Dependency reqwest 0.10.8 is significantly outdated

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

    reqwest versions

  • Dependency serde_yaml 0.8.13 has issues

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

    serde_yaml crate

  • Dependency tokio 0.2 has issues

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

    tokio crate

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

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

    Maintenance status field docs

  • Missing categories

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

    List of available categories

If some of these crates are unmaintained and shouldn't be checked, yank them or add [badges.maintenance]
status = "deprecated" to their Cargo.toml.