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.

• mlc

  • Dependency async-std 1.13.1 has issues

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

    async-std crate

  • Dependency reqwest 0.12.22 is outdated

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

    reqwest versions

  • Dependency toml 0.8.23 is outdated

    Upgrade to 1.1.0+spec-1.1.0 to get all the fixes, and avoid causing duplicate dependencies in projects.

    Easy way to bump dependencies: cargo install cargo-edit; cargo upgrade -i; Also check out Dependabot service on GitHub.

    toml versions

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["command-line-utilities", "text-processing"] 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

• grid

  • Using outdated edition for no reason

    We estimate that this crate requires at least Rust 1.62, which is newer than the last 2018-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

• fast_hilbert

  • Dependency criterion 0.7.0 is significantly outdated

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

    criterion versions

• wildmatch

  • Using outdated edition for no reason

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

    The Edition Guide

• ntest_timeout, ntest_test_cases

  • Dependency syn 1.0 is significantly outdated

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

    syn versions

• ntest_proc_macro_helper

  • 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

  • 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

• ntest_test_cases

  • Published crate doesn't match its repository

    Verified 8 out of 9 files (includes 3 Cargo-generated).

    Files in the crates.io crate compared to the repository:

    • Cargo.lock not found.
    • LICENSE does not match the repository.
    • LICENSE exists, but elsewhere in the repo.

    Looked for the crate in ntest_test_cases/. Fetched https://github.com/becheran/ntest.git tagged ntest_test_cases-v0.9.5 (b9629e5c9704402b80ff7db18813fcb65a0e2f41).

    Checked on 2025-12-21

    This check is experimental.

    Forum thread

No issues found in: ntest linkchecker

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