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.

• wthr

  • Dependency structopt 0.3.21 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 chrono-tz 0.5.3 is significantly outdated

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

    chrono-tz versions

  • Dependency colorgrad 0.4.0 is significantly outdated

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

    colorgrad versions

  • Dependency crossterm 0.20.0 is significantly outdated

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

    crossterm versions

  • Dependency geojson 0.22.2 is significantly outdated

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

    geojson versions

  • Dependency rusqlite 0.25.3 is significantly outdated

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

    rusqlite versions

  • Dependency clap 2.33.3 is outdated

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

    clap versions

  • Dependency reqwest 0.11.3 is outdated

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

    reqwest versions

  • Dependency toml 0.5.8 is outdated

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

    toml versions

• barnine

  • Dependency crossterm 0.19.0 is significantly outdated

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

    crossterm versions

  • Dependency notify =5.0.0-pre.12 is significantly outdated

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

    notify versions

  • Dependency tracing-appender 0.1.2 is significantly outdated

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

    tracing-appender versions

  • Dependency tracing-log 0.1.1 is significantly outdated

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

    tracing-log versions

  • Dependency tracing-subscriber 0.2.15 is significantly outdated

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

    tracing-subscriber versions

  • Dependency zbus =2.0.0-beta.2 is significantly outdated

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

    zbus versions

  • Dependency zbus_macros =2.0.0-beta.2 is significantly outdated

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

    zbus_macros versions

  • Dependency zvariant =2.5.0 is significantly outdated

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

    zvariant versions

  • Imprecise dependency requirement serde = 1

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

  • Locked dependency version zvariant =2.5.0

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    zvariant versions

  • Dependency swaybar-types 2.0.0 is outdated

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

    swaybar-types versions

  • Dependency toml 0.5.8 is outdated

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

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

    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 = ["network-programming"] 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

  • Missing keywords

    Help users find your crates. Add keywords = ["swaybar-protocol", "swaybar", "barnine"] (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.

• tapedeck

  • Crate contains junk files

    The crate contains boilerplate Rust files with no real functionality.

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