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.

• rs-matter

  • Dependency crypto-bigint ^0.6 is significantly outdated

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

    crypto-bigint versions

  • Dependency aes ^0.8 is a bit outdated

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

    aes versions

  • Dependency cipher ^0.4.4 is a bit outdated

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

    cipher versions

  • Dependency der ^0.7 is a bit outdated

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

    der versions

  • Dependency digest ^0.10 is a bit outdated

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

    digest versions

  • Dependency ecdsa ^0.16 is slightly outdated

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

    ecdsa versions

  • Dependency elliptic-curve ^0.13 is slightly outdated

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

    elliptic-curve versions

  • Dependency foreign-types ^0.3 is outdated

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

    foreign-types versions

  • Dependency hkdf ^0.12 is a bit outdated

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

    hkdf versions

  • Dependency hmac ^0.12 is a bit outdated

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

    hmac versions

  • Dependency nix ^0.30 is outdated

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

    nix versions

  • Dependency num-derive ^0.4 is a bit outdated

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

    num-derive versions

  • Dependency p256 ^0.13 is slightly outdated

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

    p256 versions

  • Dependency pbkdf2 ^0.12 is outdated

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

    pbkdf2 versions

  • Dependency pinned-init ^0.0.8 is outdated

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

    pinned-init versions

  • Dependency primeorder ^0.13 is slightly outdated

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

    primeorder versions

  • Dependency rand ^0.8 is outdated

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

    rand versions

  • Dependency rand_core ^0.6 is outdated

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

    rand_core versions

  • Dependency sec1 ^0.7 is slightly outdated

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

    sec1 versions

  • Dependency sha1 ^0.10 is a bit outdated

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

    sha1 versions

  • Dependency sha2 ^0.10 is a bit outdated

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

    sha2 versions

  • Dependency signature ^2.2 is a bit outdated

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

    signature versions

  • Dependency strum ^0.26 is outdated

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

    strum versions

  • Dependency x509-cert ^0.2 is slightly outdated

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

    x509-cert versions

  • Dependency zeroconf ^0.15 is outdated

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

    zeroconf versions

  • Imprecise dependency requirement async-io = ^2

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

    async-io versions

  • Optional dependency 'rand' 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 'rand', 'uuid', 'futures-lite', 'async-channel', 'crypto-bigint', 'ccm', 'aes', 'pbkdf2', 'cipher', 'hkdf', 'digest', 'sha1', 'foreign-types', 'primeorder', 'sha2', 'signature', 'x509-cert', 'libc', 'ecdsa', 'hmac', 'async-io', 'elliptic-curve', 'sec1', 'p256' may have been unintentional.

    Crate features

• rs-matter-macros

  • Dependency syn ^2 is outdated

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

    syn versions

  • Imprecise dependency requirement proc-macro-crate = ^3

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

    proc-macro-crate 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.