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.

• garfield

  • No repository property

    Specify git repository URL in Cargo.toml to help users find more information, contribute, and for lib.rs to read more info.

  • Missing categories

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

  • Using outdated edition for no reason

    We estimate that this crate requires at least Rust 1.64, 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

• zoomies

  • No repository property

    Specify git repository URL in Cargo.toml to help users find more information, contribute, and for lib.rs to read 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

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["development-tools::profiling"] to the Cargo.toml.

    List of available categories

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