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.

• ril

  • Dependency fast_image_resize ^4.0 is significantly outdated

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

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

    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

  • Dependency colorgrad ^0.6 is outdated

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

    colorgrad versions

  • Dependency fontdue ^0.7 is outdated

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

    fontdue versions

  • Dependency libwebp-sys2 ^0.1 is slightly outdated

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

    libwebp-sys2 versions

  • Failed to verify create's content against its repository

    Verified 70 out of 71 files (includes 1 Cargo-generated).

    • warning: The crates.io package has no commit hash associated with it.
      • Publish a new version, without using --allow-dirty flag. Make sure all changes are committed before publishing. Use include/exclude in Cargo.toml to omit unnecessary files.
    • warning: There is no matching git tag containing version '0.10.3'.
    • warning: Had to perform fuzzy search of the head branch due to lack of commit information in the package.

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

    • webp_convert_output.webp not found.

    Fetched https://github.com/jay3332/ril.git 3f9e3e28d3ff49b54e82fc828c62575d465acd97.

    Checked on 2025-04-28

    This check is experimental.

    Forum thread

• essence

  • Published crate doesn't match its repository

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

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

    • Cargo.lock not found.

    Fetched https://github.com/adaptchat/essence.git 12fea8c7dbb850cd14553fd2611cbb1d5c2e75cd.

    Checked on 2025-03-30

    Forum thread

  • Dependency bitflags 1.3.2 is outdated

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

    bitflags versions

  • Dependency deadpool-redis 0.15 is significantly outdated

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

    deadpool-redis versions

  • Dependency itertools 0.13 is outdated

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

    itertools versions

  • Dependency utoipa 4 is a bit outdated

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

    utoipa versions

  • Imprecise dependency requirement futures-util = 0

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

    futures-util versions

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["authentication", "text-processing"] 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 'bincode' 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 'bincode', 'utoipa', 'regex', 'serde_json' may have been unintentional.

    Crate features

• adapt

  • Dependency simd-json 0.7 is significantly outdated

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

    simd-json versions

  • Dependency tokio-tungstenite 0.18 is significantly outdated

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

    tokio-tungstenite versions

  • Published crate doesn't match its repository

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

    Fetched https://github.com/adaptchat/adapt-rs.git 2b4f538d8acc1ea24349bf2606164c3996d5185c.

    Checked on 2024-07-28

    Forum thread

  • Dependency essence 0.3 is slightly outdated

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

    essence versions

  • Dependency reqwest 0.11 is outdated

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

    reqwest versions

  • Imprecise dependency requirement bytes = 1

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

    bytes versions

  • Latest prerelease is old

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

    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

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["web-programming::http-server"] to the Cargo.toml.

    List of available categories

  • Missing keywords

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

• rdenticon

  • Missing categories

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

    List of available categories

  • Missing keywords

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

• terbium_grammar

  • Latest stable release is old

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

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

    Maintenance status field docs

  • Dependency chumsky ^0.8 is significantly outdated

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

    chumsky versions

  • Buggy README path

    The non-local path to readme specified as \.\./README\.md exposes a bug in Cargo. Please use a path inside the crate's directory. Symlinks are okay. Please verify the change doesn't break any repo-relative URLs in the README.

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["terbium", "grammar", "terbium-grammar", "compiler", "world"] (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.

• terbium

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["terbium", "compiler", "run-time", "learn", "readability"] (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.

• rs-cord

  • Crate contains junk files

    The crate contains boilerplate Rust files with no real functionality.

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