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.

• minty

  • Dependency eframe 0.17.0 is significantly outdated

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

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

    eframe versions

  • Dependency egui 0.17.0 is significantly outdated

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

    egui versions

  • Dependency egui_extras 0.17.0 is significantly outdated

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

    egui_extras versions

  • Dependency jwalk 0.5 is significantly outdated

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

    jwalk versions

  • Dependency rfd 0.7.0 is significantly outdated

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

    rfd versions

  • Dependency byte-unit 4.0.3 is outdated

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

    byte-unit versions

  • Dependency image 0.24.1 is outdated

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

    image versions

  • Imprecise dependency requirement regex = 1

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

    regex versions

  • Missing categories

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

• lexical_scanner

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["…"] to the Cargo.toml.

    List of available categories

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

    If the crate is truly stable, why not make a 1.0.0 release?

    Maintenance status field docs

  • Published crate contains binary files

    The crate contains binary files (WOFF font). Crates are meant to be compiled from source. Please check that you haven't published temporary build files by accident. If you have test fixtures, consider excluding them from crates-io tarball, since Cargo doesn't run tests from crates-io packages.

    Audit page

• fast_finder

  • Dependency clap 3.1.5 is significantly outdated

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

    clap versions

  • Dependency jwalk 0.5 is significantly outdated

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

    jwalk versions

  • Dependency colored 2 is a bit outdated

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

    colored versions

  • Imprecise dependency requirement regex = 1

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

    regex versions

  • 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

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["filesystem"] to the Cargo.toml.

    List of available categories

• lexical_scanner, minty, fast_finder

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