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.

• block_compression

  • Imprecise dependency requirement bytemuck = 1

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

    bytemuck versions

  • Optional dependency 'half' exposed as an implicit feature

    Cargo automatically makes publicly-available crate features for every optional dependency, unless the dependencies are referenced using dep: syntax. Feature 'half' may have been unintentional.

    Crate features

• sevenz-rust2

  • Failed to verify create's content against its repository

    Partially verified 66 files (includes 3 Cargo-generated).

    • warning: The crates.io package has no information about its path inside its repository.

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

    • Cargo.lock not found.

    Fetched https://github.com/hasenbanck/sevenz-rust.git tagged v0.13.2 (de024329b9fd9385fc8f7b20ea726ecedd4c7ba3).

    Checked on 2025-05-04

    This check is experimental.

    Forum thread

  • Imprecise dependency requirement byteorder = 1

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

    byteorder versions

  • Missing categories

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

  • Published crate contains binary files

    The crate contains binary files (DOS exe). Crates are meant to be compiled from source. Please check that you haven't published temporary build files by accident. If you have test fixtures, consider excluding them from crates-io tarball, since Cargo doesn't run tests from crates-io packages.

    Audit page

• egui_wgpu_backend

  • Published crate doesn't match its repository

    Partially verified 11 files (includes 3 Cargo-generated).

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

    • Cargo.lock not found.

    Fetched https://github.com/hasenbanck/egui_wgpu_backend.git 2cedc24cc58273e108b6b4605fb84d64633511e3.

    Checked on 2025-04-08

    Forum thread

  • Dependency wgpu 24.0 is outdated

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

    wgpu versions

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["rendering::graphics-api"] to the Cargo.toml.

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["back-end", "wgpu", "egui"] (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.

• romu

  • Published crate doesn't match its repository

    Partially verified 23 files (includes 3 Cargo-generated).

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

    • Cargo.lock not found.

    Fetched https://github.com/hasenbanck/romu.git 1cdac55ae56e96e6009ddb9a797b3c1a01e85ae1.

    Checked on 2024-08-04

    Forum thread

  • Dependency getrandom 0.2 is outdated

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

    getrandom versions

• lzma-rust2

  • Published crate doesn't match its repository

    Partially verified 26 files (includes 3 Cargo-generated).

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

    • Cargo.lock not found.

    Looked for the crate in lzma-rust2/. Fetched https://github.com/hasenbanck/sevenz-rust2.git tagged v0.13.2 (de024329b9fd9385fc8f7b20ea726ecedd4c7ba3).

    Checked on 2025-05-04

    Forum thread

  • Imprecise dependency requirement byteorder = 1

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

    byteorder versions

  • Missing categories

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

    List of available categories

• direct-storage

  • Dependency windows-core >=0.57, <=0.59 is significantly outdated

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

    windows-core versions

  • Dependency windows >=0.57, <=0.59 is outdated

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

    windows versions

• asche

  • Dependency erupt 0.19 is significantly outdated

    Upgrade to 0.23.0+213 to get all the fixes, and avoid causing duplicate dependencies in projects.

    erupt versions

  • Dependency raw-window-handle 0.3 is significantly outdated

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

    raw-window-handle versions

  • Latest stable release is old

    It's been over 3 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

• ppmd-sys, ppmd-rust, entangled

  • Missing categories

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

    List of available categories

• egui_winit_platform

  • Missing categories

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

    List of available categories

  • Missing keywords

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

  • Optional dependency 'copypasta' exposed as an implicit feature

    Cargo automatically makes publicly-available crate features for every optional dependency, unless the dependencies are referenced using dep: syntax. Feature 'copypasta' may have been unintentional.

    Crate features

• vk-alloc

  • Dependency parking_lot 0.11 is significantly outdated

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

    parking_lot versions

  • Dependency erupt 0.22 is outdated

    Upgrade to 0.23.0+213 to get all the fixes, and avoid causing duplicate dependencies in projects.

    erupt versions

  • Latest stable release is old

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

    Maintenance status field docs

• ppmd-sys

  • *-sys crate without links property

    If this crate uses C libraries with public symbols, consider adding links = "ppmd" to crate's Cargo.toml to avoid other libraries colliding with them. Note that the links property adds exclusivity to dependency resolution, but doesn't do any linking.

    This is also needed to protect your crate from duplicate older versions of itself. C symbols are global, and duplicate symbols can cause all sorts of breakage.

  • Imprecise dependency requirement cc = 1

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

    cc versions

• entangled

  • Dependency async-channel 1.6 is outdated

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

    async-channel versions

  • Dependency futures-lite 1.11 is outdated

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

    futures-lite versions

  • Latest stable release is old

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

    Maintenance status field docs

No issues found in: matroska-demuxer vp9-parser rand_aes

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