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.

• bvh

  • Imprecise dependency requirement serde = 1

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

  • Missing categories

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

• genact

  • Dependency instant 0.1 has issues

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

    instant crate

  • Dependency terminal_size 0.3 is significantly outdated

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

    terminal_size versions

  • Dependency yansi 0.5 is significantly outdated

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

    yansi versions

  • Dependency colorgrad 0.6.2 is outdated

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

    colorgrad versions

  • Dependency fake 2.8 is a bit outdated

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

    fake versions

  • Dependency getrandom 0.2 is outdated

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

    getrandom versions

  • Dependency rand 0.8 is a bit outdated

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

    rand versions

  • Dependency rand_distr 0.4 is slightly outdated

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

    rand_distr versions

• fints

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

  • Dependency base64 0.10.0 is significantly outdated

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

    base64 versions

  • Dependency failure 0.1 has issues

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

    failure crate

  • Dependency rand 0.6 is significantly outdated

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

    rand versions

  • Dependency reqwest 0.9 is significantly outdated

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

    reqwest versions

  • Imprecise dependency requirement serde = 1

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

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

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

    Maintenance status field docs

  • Dependency fints-institute-db 0.2 is outdated

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

    fints-institute-db versions

• proby

  • Dependency structopt 0.3 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.

    structopt crate

  • Dependency actix-rt 1.1.1 is significantly outdated

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

    actix-rt versions

  • Dependency actix-web 2.0.0 is significantly outdated

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

    actix-web versions

  • Dependency serde_with 1.4.0 is significantly outdated

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

    serde_with versions

  • Dependency simplelog 0.8 is significantly outdated

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

    simplelog versions

  • Dependency http 0.2 is outdated

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

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

    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

• proxyboi

  • Dependency actix-web 3 is significantly outdated

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

    actix-web versions

  • Dependency clap 3.0.0-beta.2 is significantly outdated

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

    clap versions

  • Dependency rustls 0.18 is significantly outdated

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

    rustls versions

  • Dependency simplelog 0.10 is significantly outdated

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

    simplelog versions

  • Dependency yansi 0.5 is significantly outdated

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

    yansi versions

  • Dependency thiserror 1 is a bit outdated

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

    thiserror versions

  • Dependency webpki 0.21 is outdated

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

    webpki versions

  • Imprecise dependency requirement actix-web = 3

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

    actix-web 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

• miniserve

  • Dependency bytesize 1 is slightly outdated

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

    bytesize versions

  • Dependency maud 0.26 is outdated

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

    maud versions

  • Dependency strum 0.26 is outdated

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

    strum versions

  • Imprecise dependency requirement actix-web = 4

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

    actix-web versions

  • Optional dependency 'rustls' 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 'rustls', 'rustls-pemfile' may have been unintentional.

    Crate features

• cargo-profiler

  • Dependency lazy_static 0.2.1 is significantly outdated

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

    lazy_static versions

  • Dependency ndarray 0.5.1 is significantly outdated

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

    ndarray versions

  • Dependency regex 0.1.69 is significantly outdated

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

    regex versions

  • Dependency rustc-serialize 0.3 has issues

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

    rustc-serialize crate

  • 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

  • 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

  • Dependency clap 2.5.1 is outdated

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

    clap versions

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["development-tools::cargo-plugins"] to the Cargo.toml.

    List of available categories

• wmfocus

  • Dependency itertools 0.12 is significantly outdated

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

    itertools versions

  • Dependency cairo-rs 0.18 is outdated

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

    cairo-rs versions

  • Optional dependency 'i3ipc' 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 'i3ipc' may have been unintentional.

    Crate features

• wiresmith, dummyhttp, genact, wmfocus

  • Imprecise dependency requirement anyhow = 1

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

    anyhow versions

• ggez

  • Dependency memoffset 0.8 is significantly outdated

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

    memoffset versions

  • Dependency wgpu 0.16 is significantly outdated

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

    wgpu versions

  • Dependency crevice 0.13 is outdated

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

    crevice versions

  • Dependency directories 5.0 is outdated

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

    directories versions

  • Dependency gilrs 0.10 is outdated

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

    gilrs versions

  • Dependency glam 0.24 is outdated

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

    glam versions

  • Dependency image 0.24 is outdated

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

    image versions

  • Dependency ordered-float 3.3 is outdated

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

    ordered-float versions

  • Dependency pollster 0.3 is outdated

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

    pollster versions

  • Dependency rodio 0.17 is outdated

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

    rodio versions

  • Dependency toml 0.5 is outdated

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

    toml versions

  • Dependency winit 0.28.3 is outdated

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

    winit versions

  • Dependency zip 0.6 is outdated

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

    zip versions

  • Optional dependency 'rodio' 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 'rodio', 'gilrs' may have been unintentional.

    Crate features

• dummyhttp

  • Dependency axum 0.7 is outdated

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

    axum versions

  • Dependency colored 2 is a bit outdated

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

    colored versions

• vulkanology

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

    Nightly crates tend to have a short lifespan. We're delisting them if they're not updated frequently.

    Maintenance status field docs

  • Dependency vulkano-shaders 0.3.2 is significantly outdated

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

    vulkano-shaders versions

  • 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

  • Missing categories

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

    List of available categories

• mt940

  • Dependency strum 0.24 is outdated

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

    strum versions

  • Dependency strum_macros 0.24 is outdated

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

    strum_macros versions

  • Dependency thiserror 1.0 is a bit outdated

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

    thiserror versions

  • Using outdated edition for no reason

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

• fints-institute-db

  • Imprecise dependency requirement regex = 1

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

    regex versions

• fints-institute-db-cli, mt940

  • Imprecise dependency requirement clap = 4

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

    clap versions

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