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.

• ccadb-crl-fetch

  • Published crate doesn't match its repository

    Partially verified 7 files (includes 3 Cargo-generated).

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

    • Cargo.lock not found.

    Looked for the crate in ccadb-crl-fetch/. Fetched https://github.com/cpu/ccadb-utils.git aaf812a24a2710fe84265424fb5b8dc83d5cc5df.

    Checked on 2024-08-10

    This check is experimental.

    Forum thread

  • Imprecise dependency requirement serde_json = 1

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

    serde_json versions

  • Dependency indicatif 0.17 is outdated

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

    In Cargo, different 0.x versions are considered incompatible, so this is a semver-major upgrade.

    indicatif versions

  • Dependency reqwest 0.12 is outdated

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

    reqwest versions

  • Missing categories

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

• ccadb-csv-fetch

  • Published crate doesn't match its repository

    Partially verified 8 files (includes 3 Cargo-generated).

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

    • Cargo.lock not found.

    Looked for the crate in ccadb-csv-fetch/. Fetched https://github.com/cpu/ccadb-utils.git aaf812a24a2710fe84265424fb5b8dc83d5cc5df.

    Checked on 2025-04-29

    Forum thread

  • Dependency rustls-webpki 0.102 is significantly outdated

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

    rustls-webpki versions

  • Dependency indicatif 0.17 is outdated

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

    indicatif versions

  • Dependency ureq 2.10 is outdated

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

    Easy way to bump dependencies: cargo install cargo-edit; cargo upgrade -i; Also check out Dependabot service on GitHub.

    ureq versions

  • Missing categories

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

    List of available categories

• webpki-root-certs

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["ca-certificate", "certificate-authorities", "trusted-root-certificate", "web-pki", "x509-certificate"] (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.

• instant-acme

  • Imprecise dependency requirement bytes = 1

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

    bytes versions

• ccadb-csv

  • Imprecise dependency requirement csv = 1

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

    csv versions

  • Missing categories

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

    List of available categories

  • No readme property

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

• libmudtelnet

  • Imprecise dependency requirement arbitrary = 1

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

    arbitrary versions

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