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.

• binstore

  • Dependency bincode ~1.1 is significantly outdated

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

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

    bincode versions

  • Dependency clap ~2.32 is significantly outdated

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

    clap versions

  • Dependency env_logger ~0.6 is significantly outdated

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

    env_logger versions

  • Dependency lz4 ~1.23 is significantly outdated

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

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

    If the crate is truly stable, why not make a 1.0.0 release?

    Maintenance status field docs

  • Missing keywords

    Help users find your crates. Add keywords = ["binstore", "header", "index", "query", "merge"] (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.

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