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.

• nuklear-rust

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

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

    Maintenance status field docs

  • Missing categories

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

• locate-locale

  • Missing categories

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

    List of available categories

• scintilla-sys

  • Dependency cc ~1.0 is significantly outdated

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

    cc versions

  • Dependency embed-resource ~1.3 is significantly outdated

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

    embed-resource versions

  • Dependency fs_extra ~1.1 is significantly outdated

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

    fs_extra versions

  • Dependency glib ^0.5 is significantly outdated

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

    glib versions

  • Dependency glib-sys ^0.6 is significantly outdated

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

    glib-sys versions

  • Dependency gobject-sys ^0.6 is significantly outdated

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

    gobject-sys versions

  • Dependency gtk ^0.4 is significantly outdated

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

    gtk versions

  • Dependency gtk-sys ^0.6 is significantly outdated

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

    gtk-sys versions

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["scintilla", "component", "scintilla-sys", "editor", "scintilla-sys-rs"] (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.

  • Published crate contains binary files

    The crate contains binary files (autotools obfuscated code, obscure autoconf code). 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

• nuklear-backend-gdi, qt_core_custom_events, anl, indep

  • Missing categories

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

    List of available categories

• nuklear-backend-gdi

  • Dependency image ~0.21 is significantly outdated

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

    image versions

  • 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

• nuklear-sys

  • Dependency cc ~1.0 is significantly outdated

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

    cc versions

  • Missing keywords

    Help users find your crates. Add keywords = ["gui", "bindings", "nuklear", "nuklear-rust", "graphics"] (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.

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

• nuklear-backend-glium

  • Dependency glium ~0.30 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.

    glium crate

  • 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

• nuklear-backend-gdi, nuklear-backend-gfx, nuklear-backend-glium, nuklear-backend-wgpurs

  • Dependency log ~0.3 is significantly outdated

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

    log versions

• anl

  • Dependency lazy_static ~0.2 is significantly outdated

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

    lazy_static versions

  • Dependency num ~0.1 is significantly outdated

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

    num versions

  • Dependency time ~0.1 is significantly outdated

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

    time versions

• nuklear-backend-wgpurs

  • Dependency glsl-to-spirv ~0.1 has issues

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

    glsl-to-spirv crate

  • Dependency wgpu ~0.4 is significantly outdated

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

    wgpu versions

• nuklear-sys, nuklear-backend-gdi, scintilla-sys, qt_core_custom_events, nuklear-backend-wgpurs

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

    It's an opportunity to update it to the current Rust edition.

    Maintenance status field docs

• nuklear-sys, nuklear-backend-gfx, nuklear-backend-glium, nuklear-backend-wgpurs

  • Missing categories

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

    List of available categories

• qt_core_custom_events

  • Missing keywords

    Help users find your crates. Add keywords = ["events", "qt-core-custom-events", "com-rust-qt-cpp-to-rust", "filtering"] (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.

  • Using outdated edition for no reason

    We estimate that this crate requires at least Rust 1.52, which is newer than the last 2015-edition compiler. You can upgrade without breaking any compatibility. Run cargo fix --edition and update edition="…" in Cargo.toml.

    Using the latest edition helps avoid old quirks of the compiler, and ensures Rust code has consistent syntax and behavior across all projects.

    The Edition Guide

• nuklear-backend-gfx

  • 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

• mcq, anl, indep

  • Latest stable release is old

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

• mcq, anl, indep

  • 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

• indep

  • Dependency log 0.3.* is significantly outdated

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

    log versions

• mcq

  • Missing categories

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

    List of available categories

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