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.

• du-dust

  • Dependency ansi_term 0.12 has issues

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

    ansi_term crate

  • Dependency lscolors 0.13 is significantly outdated

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

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

    lscolors versions

  • Dependency sysinfo 0.27 is significantly outdated

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

    sysinfo versions

  • Dependency terminal_size 0.2 is significantly outdated

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

    terminal_size versions

  • Dependency directories 4 is outdated

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

    directories versions

  • Dependency unicode-width 0.1 is a bit outdated

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

    unicode-width versions

  • Imprecise dependency requirement rayon = 1

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

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