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.

• httpd-util

  • README missing from the repository

    We've searched https://github\.com/packom/httpd\-util\.git and could not find a README file there.

  • Dependency env_logger 0.7 is significantly outdated

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

    env_logger versions

  • Dependency pnet 0.26 is significantly outdated

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

    pnet versions

  • Dependency signal-hook 0.1 is significantly outdated

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

    signal-hook 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

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

  • Dependency clap 2 is outdated

    Upgrade to 4.5.54 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

  • Imprecise dependency requirement clap = 2

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

• i2cdev2

  • Dependency nix 0.11 is significantly outdated

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

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

    Maintenance status field docs

  • Dependency bitflags 1 is outdated

    Upgrade to 2.10.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.10.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

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

    Use OR instead of /.

    SPDX license list

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["os::unix-apis"] 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 = ["ioctl", "api-access", "i2c-dev", "devices-register", "linux"] (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.

• serde-xml-rs2

  • Dependency error-chain 0.10.0 has issues

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

    error-chain crate

  • Dependency log 0.3.6 is significantly outdated

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

    log versions

  • Dependency xml-rs 0.6.0 has issues

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

    xml-rs crate

  • Dependency xmltree 0.4.0 is significantly outdated

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

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

    Maintenance status field docs

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["xml-rs", "deserialize", "deserializer-for-serde", "compatible", "debugging"] (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.

• mbus

  • Internal error

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

• mbus-api

  • Internal error

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

• pca9956b

  • Internal error

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

• i2cbus-api

  • Internal error

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

• i2cbus

  • Internal error

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

• pca9956b-api

  • Internal error

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

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