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.

• xdg-home

  • Dependency windows-sys ^0.59 is significantly outdated

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

    windows-sys versions

• zlink

  • 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 = ["varlink", "ipc", "proxy", "service", "tracing"] (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.

• gps-share

  • Dependency clap ^2.23.1 is significantly outdated

    Consider upgrading to 4.6.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.

    clap versions

  • Dependency libudev ^0.2.0 is significantly outdated

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

    libudev versions

  • Dependency serial ^0.3 is significantly outdated

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

    serial versions

  • Dependency signal-hook ^0.1.13 is significantly outdated

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

    signal-hook versions

  • Dependency zbus ^1.8 is significantly outdated

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

    zbus versions

  • Dependency zvariant ^2.6 is significantly outdated

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

    zvariant versions

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

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

    Maintenance status field docs

• firmware-controller

  • Dependency embassy-sync ^0.7.2 is outdated

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

    embassy-sync versions

  • Imprecise dependency requirement tokio = ^1

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

    tokio versions

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["controller", "actor-macro", "no-std", "firmware", "decoupling"] (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.

• mayheap

  • Imprecise dependency requirement serde = ^1

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

  • Dependency heapless ^0.8 is outdated

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

    heapless versions

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["embedded", "memory-management"] to the Cargo.toml.

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["heap-less", "vec", "fallible", "alloc", "unsafe-methods"] (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.

• zlink-core

  • Dependency winnow ^0.7 is significantly outdated

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

    winnow versions

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["varlink", "ipc", "unix-socket", "proxy", "service"] (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.

• tomling

  • Dependency winnow ^0.7.0 is significantly outdated

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

    winnow versions

• zlink-tokio

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["tokio-runtime", "proxy", "ipc", "varlink", "service"] (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.

• git-snow

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["snow", "git", "fall", "terminal", "content"] (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.

• rust-analyzer-mcp

  • Dependency env_logger ^0.10 is outdated

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

    env_logger versions

  • Dependency which ^6.0 is outdated

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

    which versions

• busd

  • Dependency quick-xml ^0.39.0 is outdated

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

    quick-xml versions

• ordered-stream

  • 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

  • Missing categories

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

    List of available categories

• firmware-controller-macros

  • Imprecise dependency requirement syn = ^2

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

    syn versions

  • No readme property

    Specify path to a README file for the project, so that information about is included in the crates.io tarball.

• zbus_systemd

  • Internal error

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

• zbus

  • Internal error

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

• gimoji

  • Internal error

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

• zlink-smol

  • Internal error

    We couldn't check this crate at this time, because: timed out validating Origin( lib.rs/crates/zlink-smol ). Please try again later.

• zbus_xmlgen

  • Internal error

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

• dbuz

  • Internal error

    We couldn't check this crate at this time, because: Crate needed for the dashboard Origin( lib.rs/crates/dbuz ). Please try again later.

• ordered-streams

  • Internal error

    We couldn't check this crate at this time, because: Crate needed for the dashboard Origin( lib.rs/crates/ordered-streams ). Please try again later.

No issues found in: zbus_xml zbus_macros zvariant zvariant_derive zvariant_utils zlink-codegen zlink-macros zbus_names endi serde-prefix-all zbus_polkit broadcast-channel dbus-macros

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