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.

• legomushroom-tun

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["…"] 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

  • Dependency ioctl-sys 0.6 is significantly outdated

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

    ioctl-sys versions

  • Dependency tokio-util 0.6 is significantly outdated

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

    tokio-util versions

  • Dependency thiserror 1 is a bit outdated

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

    thiserror versions

  • Imprecise dependency requirement byteorder = 1

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

    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.

    byteorder 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

• multiplexed-connection

  • Missing categories

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

    List of available categories

  • 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 tokio-util 0.6 is significantly outdated

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

    tokio-util versions

  • Imprecise dependency requirement anyhow = 1

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

    anyhow versions

  • Dependency connection-utils 0.2 is slightly outdated

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

    connection-utils versions

  • Dependency cs-trace 0.12 is slightly outdated

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

    cs-trace versions

  • Dependency cs-utils 0.14.0 is outdated

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

    cs-utils 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").

    Maintenance status field docs

  • Missing keywords

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

• connection-utils

  • Missing categories

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

    List of available categories

  • Imprecise dependency requirement anyhow = 1

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

    anyhow versions

  • Dependency cs-trace 0.12 is slightly outdated

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

    cs-trace versions

  • Missing keywords

    Help users find your crates. Add keywords = ["connection", "async-stream", "transfer"] (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.

• cs-utils

  • Dependency tokio-util 0.6 is significantly outdated

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

    tokio-util versions

  • Imprecise dependency requirement anyhow = 1

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

    anyhow versions

  • Dependency rand 0.8 is a bit outdated

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

    rand versions

  • Dependency thiserror 1 is a bit outdated

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

    thiserror 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 = ["random", "async-stream", "cs-utils", "utilities", "utils-rs"] (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.

• cs-trace

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

  • 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 strip-ansi-escapes 0.1.1 is outdated

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

    strip-ansi-escapes versions

  • Missing categories

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

    List of available categories

• webrtc-connection

  • Dependency tokio-util 0.6 is significantly outdated

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

    tokio-util versions

  • Dependency webrtc 0.3.1 is significantly outdated

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

    webrtc versions

  • Imprecise dependency requirement anyhow = 1

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

    anyhow versions

  • Dependency base64 0.13.0 is outdated

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

    base64 versions

  • Dependency connection-utils 0.2 is slightly outdated

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

    connection-utils versions

  • Dependency cs-trace 0.12 is slightly outdated

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

    cs-trace versions

  • Dependency cs-utils 0.14 is outdated

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

    cs-utils versions

  • Dependency rand 0.8 is a bit outdated

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

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

    Maintenance status field docs

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["webrtc-connection", "web-rtc", "connection"] (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.

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