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.

• rqueue

  • Failed to verify create's content against its repository

    Verified 5 out of 6 files (includes 2 Cargo-generated).

    • warning: Crate tarball has been published from the commit 9bd68542eac8da3ead832756aa3d542d14b15fe9, which is not in the repository.
      • Create git tags after comitting any changes, and commit changes after bumping versions and running cargo update.
    • warning: Had to perform fuzzy search of the head branch due to lack of commit information in the package.

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

    • Cargo.toml.orig does not match the repository.

    Fetched https://github.com/themanforfree/rqueue.git 19d7bf495aa8103e65b59c1d79a780c44d66cf0a.

    Checked on 2024-10-20

    This check is experimental.

    Forum thread

  • Missing categories

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

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

    Help users find your crates. Add keywords = ["rqueue"] (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.

• merged_range

  • Incorrect category

    Crate's categories property in Cargo.toml contains 'tools', which isn't a category we recognize

    lib.rs has simplified and merged some of crates.io categories. Please file a bug if we got it wrong.

    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.