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.

• entrs

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["…"] 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

  • Dependency clap 3.0.0-beta.1 is significantly outdated

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

    clap versions

  • Dependency failure 0.1.8 has issues

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

    failure crate

  • Dependency notify 5.0.0-pre.2 is outdated

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

    notify 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 = ["entr", "port", "utility", "clear", "command"] (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.

• md_render_lib

  • Dependency ansi_term ^0.12 has issues

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

    ansi_term crate

  • Dependency base64 ^0.11 is significantly outdated

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

    base64 versions

  • Dependency failure ^0.1 has issues

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

    failure crate

  • Dependency image ^0.22.4 is significantly outdated

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

    image versions

  • Dependency pulldown-cmark ^0.6 is significantly outdated

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

    pulldown-cmark versions

  • Dependency reqwest ^0.10 is significantly outdated

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

    reqwest versions

  • Dependency syntect ^3, <3.2 is significantly outdated

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

    syntect versions

  • Dependency clap ^2.33 is outdated

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

    clap versions

  • Dependency gethostname ^0.2 is outdated

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

    gethostname versions

  • Incorrect category

    Crate's categories property in Cargo.toml contains 'lib', which isn't a category we recognize

    lib.rs has simplified and merged some of crates.io categories. Please file a bug if we got it wrong.

    List of available categories

  • 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

• time-humanize

  • 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

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