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.

• cryiorust

  • Dependency askama 0.11 is significantly outdated

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

    askama versions

  • Dependency base64 0.13 is significantly outdated

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

    base64 versions

  • Dependency tiff 0.7 is significantly outdated

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

    tiff versions

  • Dependency cryiorust_derive 0.4 is slightly outdated

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

    cryiorust_derive versions

  • Dependency hdf5-bitshuffle 0.8 is slightly outdated

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

    hdf5-bitshuffle versions

  • Dependency md5 0.7 is a bit outdated

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

    md5 versions

  • Dependency ndarray 0.15 is outdated

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

    ndarray versions

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

    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 = ["multimedia::images", "compression"] 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

• hdf5-bitshuffle

  • Missing categories

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

    List of available categories

• bubbles

  • README missing from the repository

    We've searched https://git\.3lp\.cx/dyadkin/bubbles and could not find a README file there.

  • Dependency actix 0.12 is significantly outdated

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

    actix versions

  • Dependency base64 0.13 is significantly outdated

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

    base64 versions

  • Dependency daemonize 0.4 is significantly outdated

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

    daemonize versions

  • Dependency notify =5.0.0-pre.13 is significantly outdated

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

    notify versions

  • Dependency parking_lot 0.11 is significantly outdated

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

    parking_lot versions

  • Dependency tokio-util 0.6 is significantly outdated

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

    tokio-util versions

  • Dependency uuid 0.8 is significantly outdated

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

    uuid versions

  • Dependency vergen 6 is significantly outdated

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

    vergen versions

  • Dependency zstd 0.9 is significantly outdated

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

    zstd versions

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

    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

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

  • Dependency clap 2 is outdated

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

    clap versions

  • Dependency cryiorust_derive 0.4 is slightly outdated

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

    cryiorust_derive versions

  • Dependency itertools 0.10 is outdated

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

    itertools versions

  • Dependency whoami 1 is a bit outdated

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

    whoami versions

  • 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

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

    Users pay attention to the latest release date. Even if the crate is perfectly fine as-is, users may not know that.

    Maintenance status field docs

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["bubble", "server", "diffraction", "powder"] (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.

• integrustio

  • Dependency glm 0.2 is a bit outdated

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

    glm versions

  • Dependency itertools 0.10 is outdated

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

    itertools 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 = ["science", "multimedia::images"] to the Cargo.toml.

    List of available categories

• rmpfit

  • Missing categories

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

    List of available categories

No issues found in: cryiorust_derive

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