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.

• async-hid

  • Dependency async-lock 2 is significantly outdated

    Upgrade to 3.4.0 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.

    async-lock versions

  • Dependency nix 0.27 is significantly outdated

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

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

    nix versions

  • Dependency windows 0.57 is significantly outdated

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

    windows versions

  • Dependency async-channel 1 is outdated

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

    async-channel versions

  • Dependency core-foundation 0.9 is a bit outdated

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

    core-foundation versions

  • Imprecise dependency requirement async-channel = 1

    Cargo does not always pick latest versions of dependencies! Specify the version as async-channel = "2.3.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.

    async-channel versions

• betrayer

  • Dependency block2 0.5.1 is a bit outdated

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

    block2 versions

  • Dependency objc2 0.5.0 is outdated

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

    objc2 versions

  • Dependency objc2-app-kit 0.2.2 is a bit outdated

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

    objc2-app-kit versions

  • Dependency objc2-foundation 0.2.2 is a bit outdated

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

    objc2-foundation versions

  • Dependency windows-result 0.2.0 is significantly outdated

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

    windows-result versions

• embedinator, artery-font

  • 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

• com-policy-config

  • Published crate doesn't match its repository

    Verified 9 out of 10 files (includes 3 Cargo-generated).

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

    • Cargo.lock not found.
    • README.md not found.

    Fetched https://github.com/sidit77/com-policy-config.git d8174e9d33a72c24a5ae516094fbcd1f4c8d2b28.

    Checked on 2024-07-28

    This check is experimental.

    Forum thread

  • Dependency windows 0.52 is outdated

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

    windows versions

• embedinator

  • Missing keywords

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

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