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.

• h2n5

  • Dependency structopt 0.3 has issues

    It has been losing active users, which may be a sign it's deprecated or obsolete. Consider replacing it with a different crate.

    structopt crate

  • Dependency ndarray 0.13 is significantly outdated

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

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

    ndarray versions

  • Dependency actix-cors 0.6 is outdated

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

    actix-cors versions

  • Dependency env_logger 0.9 is outdated

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

    env_logger versions

  • Dependency image 0.24 is outdated

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

    image versions

  • Dependency thiserror 1.0 is a bit outdated

    Consider upgrading to 2.0.11 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 actix-web = 4

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

    actix-web versions

• n5gest

  • Dependency structopt 0.3 has issues

    It has been losing active users, which may be a sign it's deprecated or obsolete. Consider replacing it with a different crate.

    structopt crate

  • Dependency indicatif 0.13 is significantly outdated

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

    indicatif versions

  • Dependency ndarray 0.13 is significantly outdated

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

    ndarray versions

  • Dependency prettytable-rs 0.9 is significantly outdated

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

    prettytable-rs versions

  • Dependency image 0.23 is outdated

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

    image versions

  • Dependency itertools 0.10 is outdated

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

    itertools versions

  • Dependency num-derive 0.3 is outdated

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

    num-derive versions

  • Dependency tiff 0.6 is outdated

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

    tiff versions

  • Imprecise dependency requirement regex = 1

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

    regex versions

• n5

  • Dependency itertools 0.8 is significantly outdated

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

    itertools versions

  • Dependency ndarray 0.13 is significantly outdated

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

    ndarray versions

  • Dependency bzip2 0.4 is slightly outdated

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

    bzip2 versions

  • Dependency lz-fear 0.1.1 is a bit outdated

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

    lz-fear versions

  • Dependency semver 0.9 is outdated

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

    semver versions

  • Imprecise dependency requirement walkdir = 2

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

    walkdir 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

• h2n5, schemer, schemer-postgres

  • Using outdated edition for no reason

    We estimate that this crate requires at least Rust 1.56, 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

• h2n5, n5, schemer, n5gest, schemer-rusqlite, schemer-postgres, n5-wasm

  • License MIT/Apache-2.0 is not in SPDX syntax

    Use OR instead of /.

    SPDX license list

• schemer

  • Dependency thiserror 1.0 is a bit outdated

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

    thiserror versions

• schemer, schemer-rusqlite, schemer-postgres

  • Imprecise dependency requirement uuid = 1

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

    uuid versions

• n5-wasm

  • Dependency cfg-if 0.1.2 is significantly outdated

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

    cfg-if versions

  • Dependency futures 0.1.20 has issues

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

    futures crate

  • Dependency wasm-bindgen-futures 0.3.8 is significantly outdated

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

    wasm-bindgen-futures versions

  • Dependency n5 0.3.0 is outdated

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

    n5 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

• schemer-rusqlite

  • Dependency rusqlite 0.29.0 is outdated

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

    rusqlite versions

• riv, webnd, glux, chunknd, ngestd, zarr-filesystem, zarr, visag, heraclitus, ripe, ripl

  • Crate is 'reserved'

    Please be respectful of crates.io and don't squat crate names.

    It's OK if you intend to publish this project in the near future. Keep in mind that even if you have good intentions, things may not go as planned. crates.io won't reclaim abandoned crates, so reserving good names may end up wasting the good names.

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