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.

• oramfs

  • Dependency structopt 0.3.20 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 aes-gcm 0.9.2 is significantly outdated

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

    aes-gcm versions

  • Dependency argon2 0.2.1 is significantly outdated

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

    argon2 versions

  • Dependency bytes 0.6.0 is significantly outdated

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

    bytes versions

  • Dependency chacha20 0.6.0 is significantly outdated

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

    chacha20 versions

  • Dependency ctr 0.7.0 is significantly outdated

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

    ctr versions

  • Dependency env_logger 0.8.2 is significantly outdated

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

    env_logger versions

  • Dependency rand 0.7.3 is significantly outdated

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

    rand versions

  • Dependency rpassword 5.0.0 is significantly outdated

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

    rpassword versions

  • Dependency serde_yaml 0.8 has issues

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

    serde_yaml crate

  • Dependency time 0.1 is significantly outdated

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

    time versions

  • Dependency aes 0.7.4 is outdated

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

    aes versions

  • Dependency base64 0.13.0 is outdated

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

    base64 versions

  • Dependency bincode 1.3.1 is slightly outdated

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

    bincode versions

  • Dependency daemonize 0.4.1 is outdated

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

    daemonize versions

  • Dependency rand_core 0.6 is a bit outdated

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

    rand_core versions

  • Dependency runas 0.2.1 is outdated

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

    runas versions

  • Dependency shellexpand 2.1.0 is outdated

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

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

    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 = ["cryptography"] 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 = ["oram", "directory", "remote", "ftp-server", "read-write"] (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.