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.

• rusqlite

  • Dependency time ^0.3.47 is significantly outdated

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

    time versions

  • Optional dependency 'csv' exposed as an implicit feature

    Cargo automatically makes publicly-available crate features for every optional dependency, unless the dependencies are referenced using dep: syntax. Features 'csv', 'uuid', 'hashlink', 'chrono', 'jiff', 'serde_json', 'time', 'url' may have been unintentional.

    Crate features

• arcstr, atomic_float, index_vec

  • Imprecise dependency requirement serde = ^1

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

    serde versions

• more-asserts

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

    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 = ["rust-patterns"] 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

• libsqlite3-sys

  • Dependency prettyplease ^0.2.20 is slightly outdated

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

    prettyplease versions

  • Dependency syn ^2.0.89 is outdated

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

    syn versions

  • Needs more categories

    Please more specific categories that describe functionality of the crate. Expand categories = ["database", "external-ffi-bindings"] in your Cargo.toml.

    List of available categories

  • Optional dependency 'openssl-sys' exposed as an implicit feature

    Cargo automatically makes publicly-available crate features for every optional dependency, unless the dependencies are referenced using dep: syntax. Features 'openssl-sys', 'bindgen', 'syn', 'prettyplease', 'cc', 'pkg-config', 'quote', 'vcpkg' may have been unintentional.

    Crate features

• imgui-glutin-support

  • Dependency glutin >=0.17, <=0.18 is significantly outdated

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

    glutin versions

  • Dependency imgui ^0.0.21 is significantly outdated

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

    imgui versions

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

    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

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

    Use OR instead of /.

    SPDX license list

  • Missing keywords

    Help users find your crates. Add keywords = ["imgui", "glutin", "bindings-for-dear", "mouse", "size"] (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.

• index_vec

  • Dependency rkyv ^0.7 is outdated

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

    rkyv versions

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

    Use OR instead of /.

    SPDX license list

  • Using outdated edition for no reason

    We estimate that this crate requires at least Rust 1.61, which is newer than the last 2018-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

• base16, chek

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

    Maintenance status field docs

• typed-arena

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

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

    Maintenance status field docs

  • Using outdated edition for no reason

    We estimate that this crate requires at least Rust 1.42, 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.

    The Edition Guide

• divan

  • Imprecise dependency requirement clap = ^4

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

    clap versions

• ffi-support

  • 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

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

    Use OR instead of /.

    SPDX license list

• dogear

  • 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

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["bookmarks", "tree", "firefox", "algorithm", "record"] (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.

• almost, handy

  • Latest stable release is old

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

• imgui

  • Dependency bitflags ^1 is outdated

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

    bitflags versions

  • Imprecise dependency requirement bitflags = ^1

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

    Help users find your crates. Add keywords = ["dear-imgui", "font", "bindings", "back-end", "renderer"] (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.

• fast-srgb8, core_detect, nonzero_lit, smoljson

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

    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

• static_locks

  • Dependency owning_ref ^0.4 has issues

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

    owning_ref crate

  • 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

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

    Use OR instead of /.

    SPDX license list

• core_detect

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

    Use OR instead of /.

    SPDX license list

• imgui-glutin-support, termpal, cargo-repl, bad3d

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

• thin_str

  • Imprecise dependency requirement serde = ^1

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

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

    Use OR instead of /.

    SPDX license list

• handy

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

    Use OR instead of /.

    SPDX license list

• thin_str, tearor, static_locks

  • Latest stable release is old

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

• chek

  • Dependency almost ^0.1.0 is outdated

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

    almost versions

• lazy_id, unlambda, ulock-sys, cobb

  • 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

• tearor

  • Imprecise dependency requirement bytemuck = ^1

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

    bytemuck versions

• imgui-sys

  • Missing keywords

    Help users find your crates. Add keywords = ["dear", "level", "wrap", "user", "ffi"] (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.

• termpal

  • Missing categories

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

    List of available categories

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

    More info

  • 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

  • Missing keywords

    Help users find your crates. Add keywords = ["github", "future", "rgb", "squatted", "terminal-color"] (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.

• walibc

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

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["libc", "build", "bare-metal", "bundler", "wasm"] (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.

• cargo-repl, sdl-sys, more, rlm, bad3d

  • Crate contains junk files

    The crate contains boilerplate Rust files with no real functionality.

• imgui-winit-support

  • Internal error

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

• imgui-glium-renderer

  • Internal error

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

• find-places-db

  • Internal error

    We couldn't check this crate at this time, because: timed out getting crate for validation Origin( lib.rs/crates/find-places-db ). Please try again later.

No issues found in: envparse imgui-gfx-renderer startup

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