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.

• object

  • Dependency wasmparser 0.222.0 is significantly outdated

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

    wasmparser versions

  • Dependency ruzstd 0.7.0 is outdated

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

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

    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.

    flate2 versions

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["development-tools", "os", "parser-implementations"] 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

  • Optional dependency 'compiler_builtins' 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 'compiler_builtins', 'alloc', 'core' may have been unintentional.

    Crate features

  • Using outdated edition for no reason

    We estimate that this crate requires at least Rust 1.65, 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

• addr2line

  • Optional dependency 'core' 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 'core', 'alloc', 'compiler_builtins' may have been unintentional.

    Crate features

  • Using outdated edition for no reason

    We estimate that this crate requires at least Rust 1.65, 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

• gimli

  • Using outdated edition for no reason

    We estimate that this crate requires at least Rust 1.60, 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

• locate-dwarf

  • Dependency object 0.30.0 is significantly outdated

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

    object versions

  • Dependency pdb 0.7.0 is significantly outdated

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

    pdb versions

  • Dependency uuid 0.8.2 is significantly outdated

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

    uuid versions

  • Dependency core-foundation 0.9.1 is a bit outdated

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

    core-foundation 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

  • Missing keywords

    Help users find your crates. Add keywords = ["debugging", "symbols", "dwarf", "binaries", "locate"] (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.

• ddbug

  • Dependency capstone 0.12.0 is outdated

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

    capstone versions

  • Dependency capstone-sys 0.16.0 is outdated

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

    capstone-sys versions

  • Published crate contains binary files

    The crate contains binary files (ELF exe/lib). Crates are meant to be compiled from source. Please check that you haven't published temporary build files by accident. If you have test fixtures, consider excluding them from crates-io tarball, since Cargo doesn't run tests from crates-io packages.

    Audit page

• findshlibs

  • 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

  • Missing categories

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

    List of available categories

• dwarf

  • Missing categories

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

    List of available categories

  • Dependency byteorder 0.5.3 is significantly outdated

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

    byteorder versions

  • Dependency elf 0.0.9 is significantly outdated

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

    elf versions

  • Latest stable release is old

    It's been over 8 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

  • The Cargo package has no git commit information

    Before publishing a package, make sure all packaged files are committed to the repository, and there are no "dirty" files. Push this commit to crate's public repository.

    To protect against supply chain attacks similar to CVE-2024-3094, lib.rs will soon start flagging non-reproducible packages without public source code as suspicious. Currently only git repositories are supported (but may be hosted anywhere, not just GitHub). If you'd like a different SCM supported, please file a feature request.

    More info

  • License MIT/Apache-2.0 is not in SPDX syntax

    Use OR instead of /.

    SPDX license list

• ddbug_parser

  • No readme property

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

• object-rewrite

  • Dependency object 0.35.0 is significantly outdated

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

    object versions

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["object-file", "elf", "file-format", "mach-o", "modification"] (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.

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

• gkl

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["genomics", "kernel", "bindings", "forward", "alignment"] (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.