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.

• ltp

  • Dependency itertools 0.12 is significantly outdated

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

    itertools versions

  • Imprecise dependency requirement anyhow = 1

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

    anyhow versions

  • Dependency apache-avro 0.16.0 is outdated

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

    apache-avro versions

  • Dependency compact_str 0.7 is outdated

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

    compact_str versions

  • Dependency rand 0.8 is a bit outdated

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

    rand versions

  • Dependency rkyv 0.7 is a bit outdated

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

    rkyv versions

  • Missing categories

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

• gpustat

  • Dependency hostname ^0.3 is a bit outdated

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

    hostname versions

  • Dependency nix 0.26 is outdated

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

    nix versions

  • Dependency nvml-wrapper 0.9 is outdated

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

    nvml-wrapper versions

  • Dependency sysinfo 0.29 is outdated

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

    sysinfo versions

  • Dependency thiserror 1.0 is a bit outdated

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

    thiserror versions

  • Imprecise dependency requirement clap = 4

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

    clap versions

  • Missing categories

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

    List of available categories

  • Using outdated edition for no reason

    We estimate that this crate requires at least Rust 1.64, which is newer than the last 2018-edition compiler. You can upgrade without breaking any compatibility. Run cargo fix --edition and update edition="…" in Cargo.toml.

    Using the latest edition helps avoid old quirks of the compiler, and ensures Rust code has consistent syntax and behavior across all projects.

    The Edition Guide

• slurm-spank-compat

  • Missing categories

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

    List of available categories

  • Dependency bindgen 0.69 is outdated

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

    bindgen versions

• notfeed

  • Dependency clap 3.0.0-beta.2 is significantly outdated

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

    clap versions

  • Dependency clap_generate 3.0.0-beta.2 has issues

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

    clap_generate crate

  • Dependency tracing-subscriber 0.2 is significantly outdated

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

    tracing-subscriber versions

  • Dependency handlebars 4.1.2 is outdated

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

    handlebars versions

  • Dependency handlebars_misc_helpers 0.12.1 is outdated

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

    handlebars_misc_helpers versions

  • Dependency html-minifier 3 is outdated

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

    html-minifier versions

  • Dependency reqwest 0.11 is outdated

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

    reqwest versions

  • Dependency rss 1.0 is outdated

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

    rss versions

  • Imprecise dependency requirement tokio = 1

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

    tokio versions

  • 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

  • Missing categories

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

    List of available categories

• safe-rm

  • Dependency error-chain 0.12 has issues

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

    error-chain crate

  • Dependency time 0.1 is significantly outdated

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

    time versions

  • Dependency clap 2 is outdated

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

    clap versions

  • Imprecise dependency requirement clap = 2

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

    clap versions

  • 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

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

• mdbook-cms

  • Dependency md-5 0.9 is significantly outdated

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

    md-5 versions

  • Dependency serde_yaml 0.8 has issues

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

    serde_yaml crate

  • Imprecise dependency requirement anyhow = 1

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

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

    clap versions

  • Dependency indexmap 1.7 is outdated

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

    indexmap versions

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

    Maintenance status field docs

  • Missing categories

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

    List of available categories

• unlatex

  • Dependency rquickjs 0.1 is outdated

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

    rquickjs versions

  • Dependency thiserror 1.0 is a bit outdated

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

    thiserror versions

No issues found in: unlatex-cli

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