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.

• liblisa

  • Dependency bitcode 0.5.0 is significantly outdated

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

    bitcode versions

  • Dependency hashbrown 0.14.3 is significantly outdated

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

    hashbrown versions

  • Dependency itertools 0.12.0 is significantly outdated

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

    itertools versions

  • Published crate doesn't match its repository

    Partially verified 100 files (includes 3 Cargo-generated).

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

    • Cargo.lock not found.

    Looked for the crate in liblisa/. Fetched https://github.com/liblisa/liblisa.git 946ed52a22801ed438944bb0df850f464d90aecc.

    Checked on 2025-01-26

    This check is experimental.

    Forum thread

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

    Easy way to bump dependencies: cargo install cargo-edit; cargo upgrade -i; Also check out Dependabot service on GitHub.

    thiserror versions

  • Imprecise dependency requirement arbitrary = 1

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

    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.

    arbitrary versions

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["parser-implementations", "caching"] 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 = ["x86-64", "lib-lisa", "semantic", "analysis", "synthesis"] (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.

• libopcodes-rs

  • Missing categories

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

    List of available categories

  • 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

  • Missing keywords

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

  • No readme property

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

• liblisa-x64-observer

  • Missing categories

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

    List of available categories

  • Dependency itertools 0.12.0 is significantly outdated

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

    itertools versions

  • Dependency nix 0.27.1 is significantly outdated

    Upgrade to 0.30.1 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.12". 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

  • Published crate doesn't match its repository

    Verified 14 out of 15 files (includes 3 Cargo-generated).

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

    • Cargo.lock not found.
    • bootdisk.img not found.

    Looked for the crate in arch/x64/liblisa-x64-observer/. Fetched https://github.com/liblisa/liblisa.git tagged v0.1.0 (16d3c9408381ce21094a2d1cae7d4e7ca0a2c5dd).

    Checked on 2024-09-01

    Forum thread

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

    Help users find your crates. Add keywords = ["x86-64", "lib-lisa", "observer", "semantic"] (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.

  • No readme property

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

• liblisa-semantics-tool

  • Dependency itertools 0.12.0 is significantly outdated

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

    itertools versions

  • Published crate doesn't match its repository

    Partially verified 10 files (includes 3 Cargo-generated).

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

    • Cargo.lock not found.

    Looked for the crate in cli/liblisa-semantics-tool/. Fetched https://github.com/liblisa/liblisa.git b045cbeee3e3944961933ce01c3aeadad925899e.

    Checked on 2024-09-02

    Forum thread

  • Dependency bincode 1.3.3 is slightly outdated

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

    bincode versions

  • Dependency env_logger 0.10 is outdated

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

    env_logger versions

  • Dependency rand 0.8 is a bit outdated

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

    rand versions

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["semantic", "liblisa-semantics-tool", "lib-lisa", "server", "x86-64"] (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.

• rusty-xed

  • Missing categories

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

    List of available categories

  • Published crate doesn't match its repository

    Partially verified 10 files (includes 2 Cargo-generated).

    Fetched https://github.com/liblisa/rusty-xed.git 07eb451c654c700b48711e3d4a31058016642cc7.

    Checked on 2024-07-24

    Forum thread

  • Dependency xed-sys 0.5 is slightly outdated

    Consider upgrading to 0.6.0+xed-2024.05.20 to get all the fixes and improvements.

    xed-sys versions

  • Missing keywords

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

• liblisa-enc

  • Dependency itertools 0.12.0 is significantly outdated

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

    itertools versions

  • Imprecise dependency requirement thiserror = 1

    Cargo does not always pick latest versions of dependencies! Specify the version as thiserror = "2.0.12". 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 rand 0.8 is a bit outdated

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

    rand versions

  • Dependency rand_xoshiro 0.6 is a bit outdated

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

    rand_xoshiro versions

  • Dependency thiserror 1 is a bit outdated

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

    thiserror versions

  • Latest stable release is old

    It's been over 8 months. 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").

    Nightly crates tend to have a short lifespan. We're delisting them if they're not updated frequently.

    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 = ["lib-lisa", "semantic", "infer-encoding", "instructions", "analysis"] (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.

  • No readme property

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

• liblisa-x64-observer-shmqueue

  • Missing categories

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

    List of available categories

  • Failed to verify create's content against its repository

    Partially verified 9 files (includes 2 Cargo-generated).

    • warning: Crate tarball has been published from a different commit than the commit tagged by git tag 'v0.1.0'.
      • Create git tags after comitting any changes, and commit changes after bumping versions and running cargo update.

    Looked for the crate in arch/x64/liblisa-x64-observer-shmqueue/. Fetched https://github.com/liblisa/liblisa.git 8acc26fc8161dfd755efb5f6cbd4cecad3f565b1.

    Checked on 2024-08-30

    Forum thread

  • Latest stable release is old

    It's been over 8 months. 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 = ["x86-64", "lib-lisa", "semantic", "result"] (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.

  • No readme property

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

• libopcodes-sys

  • Missing categories

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

    List of available categories

  • Dependency bindgen 0.68 is significantly outdated

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

    bindgen versions

  • Missing keywords

    Help users find your crates. Add keywords = ["libopcodes-rs", "libopcodes-sys", "opcode"] (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.

  • No readme property

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

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

    Detecting docs.rs

• liblisa-synth

  • Dependency hashbrown 0.14.3 is significantly outdated

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

    hashbrown versions

  • Dependency itertools 0.12.0 is significantly outdated

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

    itertools versions

  • Imprecise dependency requirement thiserror = 1

    Cargo does not always pick latest versions of dependencies! Specify the version as thiserror = "2.0.12". 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 rand 0.8 is a bit outdated

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

    rand versions

  • Dependency rand_xoshiro 0.6 is a bit outdated

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

    rand_xoshiro versions

  • Dependency thiserror 1 is a bit outdated

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

    thiserror versions

  • Latest stable release is old

    It's been over 8 months. 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::audio"] to the Cargo.toml.

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["lib-lisa", "semantic", "oracle", "x86-64"] (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.

  • No readme property

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

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