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.

• tdorr

  • Failed to verify create's content against its repository

    Could not check any files

    • warning: The crates.io package has no information about its path inside its repository.
    • error: Repository doesn't exist: Can't checkout the repository. It's either gone or private: remote authentication required but no callback set; class=Http (34); code=Auth (-16).
      • Make sure the repository URL in Cargo.toml is correct and works with git clone. The repository must be public.

    Checked on 2026-04-19

    This check is experimental.

    Forum thread

  • Dependency serde_yaml ^0.9 has issues

    It may not be actively developed any more. Consider changing the dependency.

    serde_yaml crate

  • Imprecise dependency requirement anyhow = ^1

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

    anyhow versions

  • Dependency isomage ^0.1 is outdated

    Consider upgrading to 2.1.0 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.

    isomage versions

• hvac-transcoder

  • Imprecise dependency requirement anyhow = ^1

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

    anyhow versions

  • Dependency isomage ^0.1 is outdated

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

    isomage versions

• raic, cargo-raic, raic-build

  • Failed to verify create's content against its repository

    Could not check any files

    • warning: The crates.io package has no information about its path inside its repository.
    • error: Repository doesn't exist: Can't checkout the repository. It's either gone or private: remote authentication required but no callback set; class=Http (34); code=Auth (-16).
      • Make sure the repository URL in Cargo.toml is correct and works with git clone. The repository must be public.

    Checked on 2026-04-12

    Forum thread

• phonetics-rs

  • Imprecise dependency requirement serde = ^1

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

    serde versions

  • Published crate doesn't match its repository

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

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

    • Cargo.lock exists, but elsewhere in the repo.

    Looked for the crate in rust/phonetics/. Fetched https://github.com/jackdanger/phonetics.git tagged v0.3.1 (bce72be3c1c83e88209c33bfd995cea434783898).

    Checked on 2026-05-24

    Forum thread

• cargo-raic

  • Could not fetch repository

    We've had trouble cloning git repo from https://github\.com/jackdanger/raic\.git

    At the moment we only support git, and attempt fetching when we index a new release. Cloning is necessary for lib.rs to gather data that is missing on crates.io, e.g. to correctly resolve relative URLs in README files, which depend on repository layout and non-standard URL schemes of repository hosts.

  • No readme property

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

• gzippy

  • Dependency thiserror ^1.0 is outdated

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

    thiserror versions

  • Imprecise dependency requirement cc = ^1

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

    cc versions

  • Imprecise dependency requirement libz-ng-sys = ^1

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

    libz-ng-sys versions

  • Optional dependency 'isal-rs' exposed as an implicit feature

    Cargo automatically makes publicly-available crate features for every optional dependency, unless the dependencies are referenced using dep: syntax. Feature 'isal-rs' may have been unintentional.

    Crate features

• raic-build

  • Could not fetch repository

    We've had trouble cloning git repo from https://github\.com/jackdanger/raic\.git

  • No readme property

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

• xzippy, lazippier, jumpzippier, lazippy, bzippy2, lockzippy, pippyzippy

  • Imprecise dependency requirement thiserror = ^1

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

• xzippy

  • Failed to verify create's content against its repository

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

    • warning: The crates.io package has no information about its path inside its repository.
    • warning: There is no matching git tag containing version '0.1.0'.
      • git tag v0.1.0 4fb8d5d1fd65514af38eb5ad0b98c6e0d27d66df; git push origin --tags

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

    • Cargo.lock not found.

    Fetched https://github.com/jackdanger/xzippy.git 4fb8d5d1fd65514af38eb5ad0b98c6e0d27d66df.

    Checked on 2026-05-24

    Forum thread

  • Missing keywords

    Help users find your crates. Add keywords = ["xz", "drop-in-replacement", "umbrella", "lzma2", "format"] (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.

• xzippy, sevenzippy, lazippy, bzippy2, pippyzippy

  • Missing categories

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

• xzippy, sevenzippy, lazippier, jumpzippier, lazippy, bzippy2, lockzippy, pippyzippy

  • Dependency thiserror ^1 is outdated

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

    thiserror versions

• lockzippy

  • Dependency aes ^0.8 is a bit outdated

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

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

    aes versions

  • Dependency cbc ^0.1 is a bit outdated

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

    cbc versions

  • Dependency cipher ^0.4 is a bit outdated

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

    cipher versions

  • Dependency sha2 ^0.10 is a bit outdated

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

    sha2 versions

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["7zip", "archive", "umbrella", "key-derivation", "aes-256"] (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.

• sevenzippy

  • Imprecise dependency requirement crc32fast = ^1

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

    crc32fast versions

  • Missing keywords

    Help users find your crates. Add keywords = ["coder", "7zip", "codec", "umbrella", "archive"] (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.

• lazippier

  • 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 = ["markov-chain", "lempel-ziv-markov", "umbrella", "lzma2", "codec"] (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.

• jumpzippier

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["call", "jump", "branch", "bcj2", "umbrella"] (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.

• lazippy

  • Missing keywords

    Help users find your crates. Add keywords = ["lzma", "encode", "decode", "markov-chain", "lempel-ziv-markov"] (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.

• bzippy2

  • Missing keywords

    Help users find your crates. Add keywords = ["umbrella", "b-zip2", "compression", "bzip2", "part"] (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.

• pippyzippy

  • Missing keywords

    Help users find your crates. Add keywords = ["compression", "ppmd", "umbrella", "endian", "pure-rust"] (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 issues found in: isomage open-english-pronouncing-dictionary

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