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.

• dotter

  • Dependency handlebars 5.* is significantly outdated

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

    handlebars versions

  • Dependency toml 0.4.* is significantly outdated

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

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

    toml versions

  • Dependency watchexec-filterer-tagged 1.0.0 has issues

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

    watchexec-filterer-tagged crate

  • Dependency crossterm 0.25.0 is outdated

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

    crossterm versions

  • Dependency evalexpr 11 is outdated

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

    evalexpr versions

  • Dependency handlebars_misc_helpers 0.15.* is outdated

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

    handlebars_misc_helpers versions

  • Dependency hostname 0.3.* is outdated

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

    hostname versions

  • Dependency shellexpand 2.* is outdated

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

    shellexpand versions

  • Dependency watchexec 3 is outdated

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

    watchexec versions

  • Dependency watchexec-events 2.0.1 is outdated

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

    watchexec-events versions

  • Optional dependency 'watchexec' exposed as an implicit feature

    Cargo automatically makes publicly-available crate features for every optional dependency, unless the dependencies are referenced using dep: syntax. Features 'watchexec', 'watchexec-events', 'watchexec-filterer-tagged' may have been unintentional.

    Crate features

• devloop

  • 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 crossterm 0.18.* is significantly outdated

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

    crossterm versions

  • Dependency thiserror 1.* is a bit outdated

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

    thiserror versions

  • Dependency toml 0.5.* is outdated

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

    toml 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

  • Using outdated edition for no reason

    We estimate that this crate requires at least Rust 1.42, which is newer than the last 2015-edition compiler. You can upgrade without breaking any compatibility. Run cargo fix --edition and update edition="…" in Cargo.toml.

    Using the latest edition helps avoid old quirks of the compiler, and ensures Rust code has consistent syntax and behavior across all projects.

    The Edition Guide

• rmenu

  • Dependency conrod 0.58.* has issues

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

    conrod crate

  • Latest stable release is old

    It's been over 7 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

  • The Cargo package has no git commit information

    Before publishing a package, make sure all packaged files are committed to the repository, and there are no "dirty" files. Push this commit to crate's public repository.

    To protect against supply chain attacks similar to CVE-2024-3094, lib.rs will soon start flagging non-reproducible packages without public source code as suspicious. Currently only git repositories are supported (but may be hosted anywhere, not just GitHub). If you'd like a different SCM supported, please file a feature request.

    More info

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