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.

• kinesis

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

  • README missing from crate tarball

    Cargo sometimes fails to package the README file. Ensure the path to the README in Cargo.toml is valid, and points to a file inside the crate's directory.

  • 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

  • Missing keywords

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

• cuisiner_derive

  • Failed to verify create's content against its repository

    Verified 6 out of 12 files (includes 3 Cargo-generated).

    • warning: Crate tarball has been published from the commit 3ed09e61b193e11543131415ce3db1f4c32a7994, which is not in the repository.
      • Create git tags after comitting any changes, and commit changes after bumping versions and running cargo update.
    • warning: Found a Cargo.toml for this package in its repo (via tags), but the version was different.
      • Make sure to commit and tag after bumping the version number.
    • warning: Had to perform fuzzy search of the head branch due to lack of commit information in the package.
    • error: Manifest properties don't match: package.version.
    • warning: Cargo.toml.orig from crates.io is not an exact match with the repository.

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

    • Cargo.lock not found.
    • Cargo.toml.orig does not match the repository.
    • Cargo.toml exists, but elsewhere in the repo.
    • cuisiner_derive/src/
      • codegen.rs exists, but elsewhere in the repo.
      • analyse.rs exists, but elsewhere in the repo.
      • lower.rs exists, but elsewhere in the repo.
      • lib.rs exists, but elsewhere in the repo.
    • generics.rs exists, but elsewhere in the repo.
    • src/
      • lib.rs does not match the repository.
      • codegen.rs does not match the repository.
      • analyse.rs does not match the repository.
      • lower.rs does not match the repository.

    Looked for the crate in cuisiner_derive/. Fetched https://github.com/andogq/cuisiner.git b2dd4203032bc84770ef2b46e746592a72fa6c2e.

    Checked on 2025-04-06

    This check is experimental.

    Forum thread

  • Dependency strum 0.27.1 is outdated

    Upgrade to the latest version 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.

    strum versions

• qubit

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/qubit ) failed. Please try again later.

• qubit-macros

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/qubit-macros ) failed. Please try again later.

• cuisiner

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/cuisiner ) failed. Please try again later.

• rstrpc

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/rstrpc ) failed. Please try again later.

• rstrpc-macros

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/rstrpc-macros ) failed. Please try again later.

No issues found in: assert_layout tuple-traits

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