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.

• netlink-packet-route

  • Imprecise dependency requirement bitflags = 2

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

    bitflags versions

• netlink-packet-route, netlink-sys, rtnetlink, netlink-proto, netlink-packet-wireguard, netlink-packet-audit, netlink-packet-sock-diag, genetlink

  • 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

• rtnetlink

  • Dependency netlink-packet-route 0.19 is significantly outdated

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

    netlink-packet-route versions

  • Dependency nix 0.27.1 is significantly outdated

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

    nix versions

  • Imprecise dependency requirement thiserror = 1

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

    thiserror versions

  • Dependency async-global-executor 2.0.2 is slightly outdated

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

    async-global-executor versions

  • Dependency thiserror 1 is a bit outdated

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

    thiserror versions

  • Optional dependency 'async-global-executor' 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 'async-global-executor', 'tokio' may have been unintentional.

    Crate features

  • Using outdated edition for no reason

    We estimate that this crate requires at least Rust 1.66, which is newer than the last 2018-edition compiler. You can upgrade without breaking any compatibility. Run cargo fix --edition and update edition="…" in Cargo.toml.

    Using the latest edition helps avoid old quirks of the compiler, and ensures Rust code has consistent syntax and behavior across all projects.

    The Edition Guide

• xrl

  • Dependency bytes 0.4.12 is significantly outdated

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

    bytes versions

  • Dependency clippy 0.0.302 has issues

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

    clippy crate

  • Dependency futures 0.1.27 has issues

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

    futures crate

  • Dependency syntect 3.2.0 is significantly outdated

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

    syntect versions

  • Dependency tokio 0.1.21 has issues

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

    tokio crate

  • Dependency tokio-codec 0.1.1 has issues

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

    tokio-codec crate

  • Dependency tokio-process 0.2.3 has issues

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

    tokio-process crate

  • 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

  • Missing categories

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

    List of available categories

• netlink-proto

  • Imprecise dependency requirement thiserror = 2

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

    thiserror versions

  • Using outdated edition for no reason

    We estimate that this crate requires at least Rust 1.75, which is newer than the last 2018-edition compiler. You can upgrade without breaking any compatibility. Run cargo fix --edition and update edition="…" in Cargo.toml.

    The Edition Guide

• rmp-rpc

  • Dependency bytes ^0.4 is significantly outdated

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

    bytes versions

  • Dependency clippy ^0.0 has issues

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

    clippy crate

  • Dependency futures ^0.1 has issues

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

    futures crate

  • Dependency rmpv ^0.4 is significantly outdated

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

    rmpv versions

  • Dependency tokio ^0.1 has issues

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

    tokio crate

  • 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

• netlink-packet-utils

  • Imprecise dependency requirement thiserror = 1

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

    thiserror versions

  • Dependency thiserror 1 is a bit outdated

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

    thiserror versions

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["netlink", "macro-helpers", "message-parser", "helper"] (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.

• netlink-sys

  • Imprecise dependency requirement async-io = 2

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

    async-io versions

  • Optional dependency 'futures' 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 'futures', 'mio', 'tokio', 'async-io' may have been unintentional.

    Crate features

• netlink-packet-netfilter, netlink-packet-xfrm

  • Missing categories

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

    List of available categories

• audit

  • Imprecise dependency requirement thiserror = 1

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

    thiserror versions

  • Dependency thiserror 1 is a bit outdated

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

    thiserror versions

• netlink-packet-wireguard

  • Using outdated edition for no reason

    We estimate that this crate requires at least Rust 1.57, which is newer than the last 2018-edition compiler. You can upgrade without breaking any compatibility. Run cargo fix --edition and update edition="…" in Cargo.toml.

    The Edition Guide

• netlink-packet-sock-diag

  • Dependency bitflags 1.2.1 is outdated

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

    bitflags versions

• netlink-packet-generic

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["os::unix-apis"] to the Cargo.toml.

    List of available categories

• genetlink

  • Dependency thiserror 1.0.26 is a bit outdated

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

    thiserror versions

• audit, rmp-rpc, xfrmnetlink, netlink-packet

  • Missing categories

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

    List of available categories

• xfrmnetlink

  • Imprecise dependency requirement thiserror = 1

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

    thiserror versions

  • Dependency async-global-executor 2.0.2 is slightly outdated

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

    async-global-executor versions

  • Dependency thiserror 1 is a bit outdated

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

    thiserror versions

• netlink-packet-netfilter

  • Dependency derive_more 0.99.16 is outdated

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

    derive_more versions

• netlink-packet-core

  • Missing categories

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

    List of available categories

• cargo-heaptrack

  • Dependency cargo_metadata 0.17.0 is significantly outdated

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

    cargo_metadata versions

• ethtool

  • Failed to verify create's content against its repository

    Verified 4 out of 53 files (includes 3 Cargo-generated).

    • warning: Crate tarball has been published from the commit 96a97a737cb6250dec07766545ae04c7e456ddf3, which is not in the repository.
      • Create git tags after comitting any changes, and commit changes after bumping versions and running cargo update.
    • warning: Found a Cargo.toml for this package in its repo (via tags), but the version was different.
      • Make sure to commit and tag after bumping the version number.
    • warning: Had to perform fuzzy search of the head branch due to lack of commit information in the package.

    Files in the crates.io crate compared to the repository:

    • Cargo.toml.orig does not match the repository.
    • .gitignore does not match the repository.
    • README.md does not match the repository.
    • .rustfmt.toml not found.
    • LICENSE-MIT does not match the repository.
    • CHANGELOG does not match the repository.
    • Cargo.lock not found.
    • .github/workflows/
      • license.yml does not match the repository.
      • clippy-rustfmt.yml does not match the repository.
      • main.yml does not match the repository.
    • examples/
      • dump_features.rs not found.
      • dump_rings.rs not found.
      • dump_coalesce.rs not found.
      • dump_tsinfo.rs not found.
      • dump_pause.rs not found.
      • dump_link_mode.rs not found.
    • src/
      • connection.rs exists, but elsewhere in the repo.
      • handle.rs not found.
      • header.rs not found.
      • lib.rs not found.
      • macros.rs not found.
      • message.rs not found.
      • bitset_util.rs not found.
      • error.rs exists, but elsewhere in the repo.
    • src/coalesce/
      • get.rs not found.
      • mod.rs exists, but elsewhere in the repo.
      • handle.rs not found.
      • attr.rs not found.
    • src/feature/
      • handle.rs not found.
      • attr.rs not found.
      • get.rs not found.
      • mod.rs exists, but elsewhere in the repo.
    • src/link_mode/
      • get.rs not found.
      • handle.rs not found.
      • mod.rs exists, but elsewhere in the repo.
      • attr.rs not found.
    • src/pause/
      • attr.rs not found.
      • get.rs not found.
      • mod.rs exists, but elsewhere in the repo.
      • handle.rs not found.
    • src/ring/
      • attr.rs not found.
      • get.rs not found.
      • mod.rs exists, but elsewhere in the repo.
      • handle.rs not found.
    • src/tsinfo/
      • attr.rs not found.
      • get.rs not found.
      • handle.rs not found.
      • mod.rs not found.
    • tests/
      • get_features_lo.rs not found.
      • dump_link_modes.rs not found.

    Fetched https://github.com/little-dude/netlink.git 45ace282edcbf09dc35fe7545b5a10499ad4681a.

    Checked on 2024-08-04

    This check is experimental.

    Forum thread

  • No repository property

    Specify git repository URL in Cargo.toml to help users find more information, contribute, and for lib.rs to read more info.

  • Dependency thiserror 1.0.29 is a bit outdated

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

    thiserror versions

• netlink-packet

  • Dependency bytes 0.4.11 is significantly outdated

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

    bytes versions

  • Dependency failure 0.1.3 has issues

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

    failure crate

  • Dependency netlink-sys 0.1 is significantly outdated

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

    netlink-sys versions

  • Buggy README path

    The non-local path to readme specified as \.\./README\.md exposes a bug in Cargo. Please use a path inside the crate's directory. Symlinks are okay. Please verify the change doesn't break any repo-relative URLs in the README.

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

No issues found in: iproute2 netlink-socket netlink-ip ipaddr tayar

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