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.

• cargo-launcher

  • Dependency structopt 0.2 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 pretty_env_logger 0.3 is significantly outdated

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

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

    pretty_env_logger versions

  • Dependency tempdir 0.3 has issues

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

    tempdir crate

  • Dependency tera 0.11 is significantly outdated

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

    tera versions

  • Dependency dirs 1.0 is outdated

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

    dirs versions

  • Dependency zip 0.5 is outdated

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

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

    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 = ["command-line-utilities"] 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 = ["register", "launcher", "cargo", "alfred", "binary"] (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.

• ccclog

  • 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 itertools 0.9 is significantly outdated

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

    itertools versions

  • Dependency serde_yaml 0.8 has issues

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

    serde_yaml crate

  • Dependency strum 0.18 is significantly outdated

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

    strum versions

  • Dependency strum_macros 0.18 is significantly outdated

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

    strum_macros versions

  • Dependency git2 0.13 is outdated

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

    git2 versions

  • Dependency pretty_env_logger 0.4 is outdated

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

    pretty_env_logger versions

  • Dependency semver 0.9 is outdated

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

    semver versions

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

    Use OR instead of /.

    SPDX license list

• bump-bin

  • Imprecise dependency requirement anyhow = 1

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

    This crate does not bump semver-minor when adding new features, so to be safe you get all the features/APIs/fixes that your crate depends on, require a more specific patch version.

    anyhow versions

• blackhole-bin

  • Dependency clap-verbosity-flag 2 is outdated

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

    clap-verbosity-flag versions

  • Dependency colored_json 3.2 is outdated

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

    colored_json versions

  • Dependency fern 0.6 is outdated

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

    fern 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

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