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.

• ord-by-set, panda-channels

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

    Users pay attention to the latest release date. Even if the crate is perfectly fine as-is, users may not know that.

    Maintenance status field docs

• panda-re

  • 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 dashmap 4 is significantly outdated

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

    dashmap versions

  • Dependency dirs 3.0.1 is significantly outdated

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

    dirs versions

  • Dependency glib-sys 0.10.0 is significantly outdated

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

    glib-sys versions

  • Dependency inventory 0.1.8 is significantly outdated

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

    inventory versions

  • Dependency libloading 0.6.2 is significantly outdated

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

    libloading versions

  • Dependency parking_lot 0.11 is significantly outdated

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

    parking_lot versions

  • Dependency strum 0.20 is significantly outdated

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

    strum versions

  • Dependency strum_macros 0.20 is significantly outdated

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

    strum_macros versions

  • No readme property

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

  • Dependency thiserror 1 is outdated

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

    thiserror versions

  • Imprecise dependency requirement array-init = 2

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

    array-init versions

  • Missing keywords

    Help users find your crates. Add keywords = ["dynamic-analysis", "panda", "syscalls", "callback", "bindings"] (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.

  • Optional dependency 'dashmap' 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 'dashmap', 'async-trait', 'log', 'parking_lot' may have been unintentional.

    Crate features

• panda-channels

  • Missing categories

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

    List of available categories

  • Dependency cbindgen 0.19 is significantly outdated

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

    cbindgen versions

  • Dependency parking_lot 0.11.1 is significantly outdated

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

    parking_lot versions

  • Imprecise dependency requirement lazy_static = 1

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

    lazy_static versions

  • Missing keywords

    Help users find your crates. Add keywords = ["hypervisor", "plugin", "channel", "guest", "communicating"] (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.

• qcow

  • Dependency zstd 0.9.0 is significantly outdated

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

    zstd versions

  • Dependency modular-bitfield 0.11.2 is a bit outdated

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

    modular-bitfield versions

  • Dependency thiserror 1 is outdated

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

    thiserror versions

  • Imprecise dependency requirement flate2 = 1

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

    flate2 versions

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

    Maintenance status field docs

  • Missing categories

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

    List of available categories

• qcow-cli

  • Dependency structopt 0.3.22 has issues

    It has been losing active users, which may be a sign it's deprecated or obsolete. Consider replacing it with a different crate.

    structopt crate

  • Dependency owo-colors 2.0.0 is significantly outdated

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

    owo-colors versions

  • Dependency syntect 4.5.0 is significantly outdated

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

    syntect versions

  • Dependency tabled 0.2.2 is significantly outdated

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

    tabled versions

  • docs.rs build failed

    docs.rs site failed to build the crate, so users will have trouble finding the documentation. Docs.rs supports multiple platforms and custom configurations, so you can make the build work even if normal crate usage has special requirements.

    Docs.rs doesn't need to run or even link any code, so system dependencies can simply be skipped. You can also set cfg() flags just for docs.rs and use them to hide problematic code.

    Detecting docs.rs

  • Dependency bat 0.18.2 is outdated

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

    bat versions

  • Dependency bootsector 0.1.5 is outdated

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

    bootsector versions

  • Dependency humansize 1.1.1 is outdated

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

    humansize versions

  • Dependency positioned-io 0.2 is outdated

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

    positioned-io versions

  • Missing categories

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

    List of available categories

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

• panda-re-sys

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

  • *-sys crate without links property

    If this crate uses C libraries with public symbols, consider adding links = "panda-re" to crate's Cargo.toml to avoid other libraries colliding with them. Note that the links property adds exclusivity to dependency resolution, but doesn't do any linking.

    This is also needed to protect your crate from duplicate older versions of itself. C symbols are global, and duplicate symbols can cause all sorts of breakage.

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["dynamic-analysis", "panda", "path", "platform", "interfacing"] (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.

• panda-re-macros

  • 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 darling 0.10.2 is significantly outdated

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

    darling versions

  • Dependency syn 1.0.37 is significantly outdated

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

    syn versions

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

• gpt-partition-type

  • 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 = ["algorithms"] to the Cargo.toml.

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["gpt-partition", "guid", "information", "information-about-gpt-partition", "os"] (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.