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.

• ar_archive_writer

  • Dependency object 0.37.1 is slightly outdated

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

    In Cargo, different 0.x versions are considered incompatible, so this is a semver-major upgrade.

    object versions

  • Missing categories

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

• twiggy

  • Dependency structopt 0.3 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

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

    Use OR instead of /.

    SPDX license list

  • Missing keywords

    Help users find your crates. Add keywords = ["code-size", "profiler", "wasm", "wasm-binary"] (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.

  • 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

• libbz2-rs-sys-cdylib

  • Failed to verify create's content against its repository

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

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

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

    • Cargo.lock does not match the repository.

    Looked for the crate in libbz2-rs-sys-cdylib/. Fetched https://github.com/trifectatechfoundation/libbzip2-rs.git de9e3598d9eb9e608e799839e01964dcd6b6fc33.

    Checked on 2025-08-10

    This check is experimental.

    Forum thread

  • Missing keywords

    Help users find your crates. Add keywords = ["cdylib", "libbz2", "drop-in", "compression", "replace"] (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.

• bzip2-sys

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

    Use OR instead of /.

    SPDX license list

  • Missing keywords

    Help users find your crates. Add keywords = ["compression", "decompression", "libbz2", "libbzip2"] (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.

  • Needs more categories

    Please more specific categories that describe functionality of the crate. Expand categories = ["compression", "external-ffi-bindings"] in your Cargo.toml.

    List of available categories

  • No readme property

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

  • Using outdated edition for no reason

    We estimate that this crate requires at least Rust 1.51, which is newer than the last 2015-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

• pretty_backtrace

  • Dependency addr2line 0.9.0 is significantly outdated

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

    addr2line versions

  • Dependency findshlibs 0.4.0 is significantly outdated

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

    findshlibs versions

  • Dependency gimli 0.18.0 is significantly outdated

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

    gimli versions

  • Dependency object 0.12.0 is significantly outdated

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

    object versions

  • Dependency syntect 3.0.2 is significantly outdated

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

    syntect versions

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

    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 = ["development-tools::debugging"] to the Cargo.toml.

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["backtrace", "pretty", "force-setup", "colored", "panic"] (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.

• sudo-rs

  • Missing keywords

    Help users find your crates. Add keywords = ["memory-safety", "su", "audit", "linux", "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.

• libbz2-rs-sys

  • Missing keywords

    Help users find your crates. Add keywords = ["compression", "bzip2", "api-compatible", "part", "drop-in"] (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.

• libbz2-rs-sys, libbz2-rs-sys-cdylib, libzstd-rs-sys

  • Missing categories

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

    List of available categories

• split_tokens

  • Latest stable release is old

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

  • Missing categories

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

    List of available categories

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

  • Missing keywords

    Help users find your crates. Add keywords = ["zstd", "compression", "decompression", "work-in-progress", "ready"] (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.

• slog-notify

  • Missing categories

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

    List of available categories

  • Dependency notify-rust 3.2 is significantly outdated

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

    notify-rust versions

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

    More info

  • Imprecise dependency requirement slog = 2

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

    slog versions

• rustc_codegen_cranelift

  • Crate is 'reserved'

    Please be respectful of crates.io and don't squat crate names.

    It's OK if you intend to publish this project in the near future. Keep in mind that even if you have good intentions, things may not go as planned. crates.io won't reclaim abandoned crates, so reserving good names may end up wasting the good names.

  • 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: bzip2

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