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.

• hidamari

  • Dependency alsa 0.4.2 is significantly outdated

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

    In Cargo, different 0.x versions are considered incompatible, so this is a semver-major upgrade.

    alsa versions

  • Dependency bytes 0.5 is significantly outdated

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

    Easy way to bump dependencies: cargo install cargo-edit; cargo upgrade -i; Also check out Dependabot service on GitHub.

    bytes versions

  • Dependency dbus 0.8.4 is significantly outdated

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

    dbus versions

  • Dependency dbus-crossroads 0.2.1 is significantly outdated

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

    dbus-crossroads versions

  • Dependency dbus-tokio 0.5.2 is significantly outdated

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

    dbus-tokio versions

  • Dependency hyper 0.13 is significantly outdated

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

    hyper versions

  • Dependency id3 0.5.1 is significantly outdated

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

    id3 versions

  • Dependency lru 0.6.0 is significantly outdated

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

    lru versions

  • Dependency mp4ameta 0.3.0 is significantly outdated

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

    mp4ameta versions

  • Dependency nix 0.15.0 is significantly outdated

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

    nix versions

  • Dependency num-complex 0.3.0 is significantly outdated

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

    num-complex versions

  • Dependency rand 0.7.3 is significantly outdated

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

    rand versions

  • Dependency roxmltree 0.13.0 is significantly outdated

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

    roxmltree versions

  • Dependency serde_urlencoded 0.6.1 is significantly outdated

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

    serde_urlencoded versions

  • Dependency tokio 0.2.6 has issues

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

    tokio crate

  • Dependency tokio-util 0.3.1 is significantly outdated

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

    tokio-util versions

  • Dependency warp 0.2 is significantly outdated

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

    warp versions

  • Dependency headers 0.3 is a bit outdated

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

    headers versions

  • Dependency pretty_env_logger 0.4.0 is outdated

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

    pretty_env_logger versions

  • Dependency rupnp 0.1.6 is outdated

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

    rupnp versions

  • Dependency toml 0.5 is outdated

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

    toml versions

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

    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.

    regex versions

  • Missing categories

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

• fft_bench

  • Dependency num-complex 0.3.0 is significantly outdated

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

    num-complex versions

  • Dependency pretty_env_logger 0.4.0 is outdated

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

    pretty_env_logger versions

• mpdsh

  • Dependency wildmatch 1.0.10 is significantly outdated

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

    wildmatch versions

  • Dependency rustyline 6.2.0 is outdated

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

    rustyline versions

  • Dependency rustyline-derive 0.3.1 is outdated

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

    rustyline-derive versions

  • 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

• hidamari, fft_bench, mpdsh

  • 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

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