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.

• kira_cdh_compat_fastq_reader

  • Imprecise dependency requirement tokio = 1

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

    tokio versions

  • Optional dependency 'async-compression' 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 'async-compression', 'tokio', 'memmap2' may have been unintentional.

    Crate features

• kira_kv_engine

  • Imprecise dependency requirement serde = 1

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

  • Published crate doesn't match its repository

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

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

    • Cargo.lock not found.

    Fetched https://github.com/aryaskov/kira_kv_engine.git add49831b5ea023a5f9e9e6ac871a409a3787a2f.

    Checked on 2025-08-17

    This check is experimental.

    Forum thread

  • Dependency bincode 1 is a bit outdated

    Consider upgrading to 2.0.1 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.

    bincode versions

  • Dependency rand 0.8 is outdated

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

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

    rand versions

• kira-cdh

  • Published crate doesn't match its repository

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

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

    • Cargo.lock not found.

    Fetched https://github.com/aryaskov/kira-cdh.git 759e9eaf6c431f4c0f31bfd4f8253350b85d1213.

    Checked on 2025-08-24

    Forum thread

  • Dependency indicatif 0.17 is a bit outdated

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

    indicatif versions

  • Dependency itertools 0.13 is outdated

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

    itertools versions

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["science::bio"] 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 = ["fasta", "cd-hit", "k-mer", "replace", "single-binary"] (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.

• kira_cdh_compat_cluster

  • Imprecise dependency requirement anyhow = 1

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

  • Optional dependency 'rayon' exposed as an implicit feature

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

    Crate features

• kira_kv_engine, kira-cdh, kira_cdh_compat_lsh, minimal_perfect_hash

  • Dependency hashbrown 0.14 is significantly outdated

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

    hashbrown versions

• minimal_perfect_hash

  • Imprecise dependency requirement serde = 1

    Cargo does not always pick latest versions of dependencies! Specify the version as serde = "1.0.228". 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 bincode 1 is a bit outdated

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

    bincode versions

  • Dependency rand 0.8 is outdated

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

    rand versions

• kira_cdh_compat_fastq_reader, kira_kv_engine, minimal_perfect_hash

  • Dependency thiserror 1 is outdated

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

    thiserror versions

• kira_cdh_compat_kmer_indexer

  • Optional dependency 'bytemuck' 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 'bytemuck', 'memmap2', 'tokio' may have been unintentional.

    Crate features

• kira_cdh_compat_kmer_indexer, kira-cdh, kira_cdh_compat_lsh

  • Dependency thiserror 1.0 is outdated

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

    thiserror versions

• kira_cdh_compat_lsh

  • Imprecise dependency requirement rustc-hash = 2

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

    rustc-hash versions

No issues found in: kira_cdh_compat_clstr pgm_index get_dir_hash

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