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.

• zssh

  • Dependency constant_time_eq 0.3 is a bit outdated

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

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

    constant_time_eq versions

  • Dependency rand 0.8 is a bit outdated

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

    rand versions

• img2raw-tools

  • 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 failure 0.1 has issues

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

    failure crate

  • Dependency image 0.22 is significantly outdated

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

    image versions

  • Dependency zerocopy 0.2 is significantly outdated

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

    zerocopy versions

  • Dependency half 1.3 is outdated

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

    half versions

  • Missing keywords

    Help users find your crates. Add keywords = ["data", "pixel", "color-space", "convert-images", "image"] (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.

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

• lpc11xx-async-hal, lpc11xx, vblk, img2raw-tools, core-futures-stateless, quasi-rd

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

    Nightly crates tend to have a short lifespan. We're delisting them if they're not updated frequently.

    Maintenance status field docs

• vblk

  • Dependency crossbeam-utils 0.7 is significantly outdated

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

    crossbeam-utils versions

  • Dependency nix 0.16 is significantly outdated

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

    nix versions

  • Dependency zerocopy 0.2 is significantly outdated

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

    zerocopy versions

• img2raw

  • Dependency zerocopy 0.2 is significantly outdated

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

    zerocopy 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 keywords

    Help users find your crates. Add keywords = ["pixel", "color-space", "data", "raw", "header"] (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.

• lpc11xx-async-hal

  • Dependency cortex-m 0.6.0 is significantly outdated

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

    cortex-m versions

  • Dependency lpc11xx 0.1.4 is slightly outdated

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

    lpc11xx versions

• lpc11xx

  • Dependency cortex-m 0.6 is significantly outdated

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

    cortex-m versions

  • Dependency bare-metal 0.2 is outdated

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

    bare-metal versions

  • Dependency cortex-m-rt 0.6 is outdated

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

    cortex-m-rt versions

• lpc550x

  • Dependency cortex-m-rt 0.6.13 is outdated

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

    cortex-m-rt versions

• quasi-rd

  • Dependency num-bigint 0.2 is significantly outdated

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

    num-bigint versions

  • Dependency num-rational 0.2 is outdated

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

    num-rational versions

• core-futures-stateless

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["asynchronous"] 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 = ["context", "workaround", "task", "async-await", "future"] (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.

No issues found in: max32660 zerocrush

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