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.

• glow

  • Imprecise dependency requirement slotmap = 1

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

    slotmap versions

  • Missing keywords

    Help users find your crates. Add keywords = ["opengl", "webgl", "run-gl", "anywhere", "target-specific"] (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.

• glow, glyphon, spirv_cross, metal-rs, wgpu-native, gfx-auxil, gfx-backend-gl, gfx-backend-vulkan, gfx-hal, gfx-backend-empty

  • Missing categories

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

• glyphon

  • Dependency cosmic-text 0.18 is significantly outdated

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

    cosmic-text versions

  • Dependency lru 0.16.2 is outdated

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

    lru versions

  • Missing keywords

    Help users find your crates. Add keywords = ["text-rendering", "wgpu", "texture-atlas", "wgpu-rendering", "2d-rendering"] (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.

• metal-rs

  • Dependency cocoa 0.15 has issues

    It may not be actively developed any more. Consider changing the dependency.

    cocoa crate

  • Latest stable release is old

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

    If the crate is truly stable, why not make a 1.0.0 release?

    Maintenance status field docs

  • 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

  • docs.rs build failed

    docs.rs site failed to build the crate, so users will have trouble finding the documentation. Docs.rs supports multiple platforms and custom configurations, so you can make the build work even if normal crate usage has special requirements.

    Docs.rs doesn't need to run or even link any code, so system dependencies can simply be skipped. You can also set cfg() flags just for docs.rs and use them to hide problematic code.

    Detecting docs.rs

  • Dependency bitflags 1 is outdated

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

    bitflags versions

  • Dependency foreign-types 0.3 is a bit outdated

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

    foreign-types versions

  • Imprecise dependency requirement bitflags = 1

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

    bitflags versions

• gfx-backend-gl

  • Dependency gfx-auxil 0.10 has issues

    It has been losing active users, which may be a sign it's deprecated or obsolete. Consider replacing it with a different crate.

    gfx-auxil crate

  • Dependency glow 0.9 is significantly outdated

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

    glow versions

  • Dependency libloading 0.7 is significantly outdated

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

    libloading versions

  • Dependency parking_lot 0.11 is significantly outdated

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

    parking_lot versions

  • Dependency bitflags 1 is outdated

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

    bitflags versions

  • Dependency khronos-egl 4.1 is outdated

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

    khronos-egl versions

  • Imprecise dependency requirement bitflags = 1

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

    bitflags versions

• metal

  • Imprecise dependency requirement bitflags = 2

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

    bitflags versions

  • Missing categories

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

    List of available categories

• wgpu-native

  • Dependency parking_lot 0.10 is significantly outdated

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

    parking_lot versions

  • Dependency wgpu-core 0.5 is significantly outdated

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

    wgpu-core versions

  • Dependency wgpu-types 0.5 is significantly outdated

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

    wgpu-types versions

  • Latest stable release is old

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

• decline-curve-analysis

  • Imprecise dependency requirement thiserror = 2

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

    This crate does not bump semver-minor when adding new features, so to be safe you get all the features/APIs/fixes that your crate depends on, require a more specific patch version.

    thiserror versions

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["analysis", "curve", "decline", "equation", "utilities"] (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.

• spirv_cross

  • Buggy README path

    The non-local path to readme specified as \.\./README\.md exposes a bug in Cargo. Please use a path inside the crate's directory. Symlinks are okay. Please verify the change doesn't break any repo-relative URLs in the README.

  • Imprecise dependency requirement cc = 1

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

  • Latest stable release is old

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

  • License MIT/Apache-2.0 is not in SPDX syntax

    Use OR instead of /.

    SPDX license list

• spirv_cross, wgpu-native, gfx-auxil, gfx-hal, gfx-backend-empty

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

• sbdf

  • Imprecise dependency requirement thiserror = 2

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

    thiserror versions

  • Published crate doesn't match its repository

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

    • error: Repository doesn't exist: Can't checkout the repository. It's either gone or private: remote authentication required but no callback set; class=Http (34); code=Auth (-16).
      • Make sure the repository URL in Cargo.toml is correct and works with git clone. The repository must be public.

    Fetched https://github.com/pod2co/sbdf.git d81575cbded9ffb5b2b37a3192bc41acd006c747.

    Checked on 2025-05-04

    This check is experimental.

    Forum thread

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["binary-data-format", "spotfire", "reader-writer", "file-writer", "file-format"] (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.

• gfx-backend-vulkan

  • Dependency ash 0.32 is significantly outdated

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

    ash versions

  • Dependency parking_lot 0.11 is significantly outdated

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

    parking_lot versions

  • Dependency core-graphics-types 0.1 is a bit outdated

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

    core-graphics-types versions

  • 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

• gfx-auxil

  • Reported security advisory RUSTSEC-2021-0091

    Reading on uninitialized buffer may cause UB ( `gfx_auxil::read_spirv()` )

    All crate audits

• gfx-auxil, gfx-backend-gl, gfx-backend-vulkan, gfx-backend-empty

  • Dependency gfx-hal 0.9 has issues

    It has been losing active users, which may be a sign it's deprecated or obsolete. Consider replacing it with a different crate.

    gfx-hal crate

• wgpu-native, gfx-backend-gl, gfx-backend-vulkan

  • Dependency arrayvec 0.5 is significantly outdated

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

    arrayvec versions

• wgpu-native, gfx-backend-gl, gfx-backend-vulkan, gfx-hal, gfx-backend-empty

  • 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

• gfx-backend-empty

  • 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 = ["testing", "back-end", "gfx-rs", "graphics-back-end", "mocking"] (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.

• gfx-hal

  • Imprecise dependency requirement serde = 1

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

    serde versions

  • Dependency bitflags 1.0 is outdated

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

    bitflags versions

  • Dependency thiserror 1 is outdated

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

    thiserror versions

• gfx-backend-gl, gfx-backend-vulkan, gfx-hal

  • Dependency naga 0.5 is significantly outdated

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

    naga versions

• gfx-auxil, gfx-backend-gl, gfx-backend-vulkan, gfx-hal, gfx-backend-empty

  • 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

• gfx-backend-dx12

  • Internal error

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

• gfx-backend-metal

  • Internal error

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

• gfx-backend-dx11

  • Internal error

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

No issues found in: range-alloc

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