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.

• genify

  • Imprecise dependency requirement url = ^2

    Cargo does not always pick latest versions of dependencies! Specify the version as url = "2.5.0". If Cargo.lock ends up having an unexpectedly old version of the dependency, you might get a dependency that lacks features/APIs or important bugfixes that you depend on. This is most likely to happen when using the minimal-versions flag, used by users of old Rust versions.

    If you want to keep using truly minimal dependency requirements, please make sure you test them in CI with -Z minimal-versions Cargo option, because it's very easy to accidentally use a feature added in a later version.

    url versions

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["artificial-intelligence"] 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 = ["turn", "mcp", "coding-agents", "generator", "diff"] (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.

• kdbx

  • Dependency keepass ^0.12 is significantly outdated

    Consider upgrading to 0.13.20 to get all the fixes and improvements.

    In Cargo, different 0.x versions are considered incompatible, so this is a semver-major upgrade.

    keepass versions

  • Dependency skim ^1.3 is significantly outdated

    Consider upgrading to 5.6.0 to get all the fixes and improvements.

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

    skim versions

  • Imprecise dependency requirement security-framework = ^3

    Cargo does not always pick latest versions of dependencies! Specify the version as security-framework = "3.7.0". If Cargo.lock ends up having an unexpectedly old version of the dependency, you might get a dependency that lacks features/APIs or important bugfixes that you depend on. This is most likely to happen when using the minimal-versions flag, used by users of old Rust versions.

    security-framework versions

• github-actions

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["action", "debugging", "summary", "input", "group"] (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.

• taskline

  • Dependency redis ^0.28 is significantly outdated

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

    redis versions

• mockser

  • Dependency axum ^0.7.5 is outdated

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

    axum versions

  • Dependency config ^0.14.0 is outdated

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

    config versions

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["network-programming"] to the Cargo.toml.

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["testing", "mocking", "mocking-server", "mock-server", "host-port"] (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.

• sportorg

  • Failed to verify create's content against its repository

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

    • warning: Crate tarball has been published from the commit eb9b72f7e825d1813e0ba94e708e01e9687ad9de, 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.
    • error: Manifest properties don't match: Existence of [lib] inconsistent: published=true; orig=false.

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

    • .gitignore does not match the repository.
    • Cargo.toml not found.
    • lib.rs exists, but elsewhere in the repo.

    Fetched https://github.com/sportorg/pysport.git b5ea9fb7bebdd99a6410961fdfd3228fa28b2581.

    Checked on 2024-12-29

    This check is experimental.

    Forum thread

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["competition", "orienteering", "python", "solution", "execution"] (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.

  • No readme property

    Specify path to a README file for the project, so that information about is included in the crates.io tarball.

• casense, dany, tinkoff

  • Crate contains junk files

    The crate contains boilerplate Rust files with no real functionality.

• tinkoff

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

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