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.

• appendlist

  • Latest stable release is old

    It's been over 5 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").

    Users pay attention to the latest release date. Even if the crate is perfectly fine as-is, users may not know that.

    Maintenance status field docs

  • Missing categories

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

  • Missing keywords

    Help users find your crates. Add keywords = ["list", "reference", "insertion", "elements", "vec"] (up to 5) to the Cargo.toml. Best keywords are alternative terms or their spellings that aren't in the name or description. Also add a keyword that precisely categorizes this crate and groups it with other similar crates.

• windows-permissions

  • Internal error

    We couldn't check this crate at this time, because: Crate needed for the dashboard Origin( lib.rs/crates/windows-permissions ). Please try again later.

• repr-trait

  • Internal error

    We couldn't check this crate at this time, because: Crate needed for the dashboard Origin( lib.rs/crates/repr-trait ). Please try again later.

• repr-trait-derive

  • Internal error

    We couldn't check this crate at this time, because: Crate needed for the dashboard Origin( lib.rs/crates/repr-trait-derive ). Please try again later.

• intcode

  • Internal error

    We couldn't check this crate at this time, because: Crate needed for the dashboard Origin( lib.rs/crates/intcode ). Please try again later.

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