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.

• axotag

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["development-tools::build-utils", "compilers"] 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 = ["tags", "tag-parsing", "share", "parser", "project"] (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.

• cue

  • Published crate doesn't match its repository

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

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

    • Cargo.lock not found.

    Fetched https://github.com/mistydemeo/libcue.rs.git 5ca637d9fa30cd507c18babe3888e7c2d828d71b.

    Checked on 2025-06-01

    This check is experimental.

    Forum thread

  • 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

• cargo-dist

  • Dependency cargo_metadata 0.19.2 is outdated

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

    cargo_metadata versions

  • Dependency clap-cargo 0.14.1 is outdated

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

    clap-cargo versions

  • Dependency color-backtrace 0.6.1 is outdated

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

    color-backtrace versions

  • Dependency console 0.15.10 is a bit outdated

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

    console versions

  • Dependency dialoguer 0.11.0 is outdated

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

    dialoguer versions

  • Dependency goblin 0.8.2 is outdated

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

    goblin versions

  • Dependency schemars 0.8.22 is outdated

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

    schemars versions

  • Dependency spdx 0.10.9 is a bit outdated

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

    spdx versions

  • Imprecise dependency requirement uuid = 1

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

    uuid versions

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["development-tools::cargo-plugins"] to the Cargo.toml.

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["setup", "build", "publish", "binaries", "install"] (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.

• cue-sys

  • Could not fetch repository

    We've had trouble cloning git repo from https://github\.com/mistydemeo/libcue\.rs\.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.

  • Failed to verify create's content against its repository

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

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

    Looked for the crate in cue-sys/. Fetched https://github.com/mistydemeo/libcue.rs.git 11b9427ab3acebbaa8b3e34facef3afdb4a05305.

    Fetched submodule cue-sys/vendor/libcue from https://github.com/lipnitsk/libcue.git cfb98a060fd79dbc3463d85f0f29c3c335dfa0ea.

    Checked on 2024-12-01

    Forum thread

  • 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

• cdrom_crc

  • Missing categories

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

    List of available categories

• sega_cmp, cdrom_crc, sega_film, fldtools

  • 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

• sega_cmp, cdrom_crc, sega_film

  • Latest stable release is old

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

• sega_cmp, pafe-sys, sega_film, dist

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

• fldtools

  • Dependency itertools 0.6.1 is significantly outdated

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

    itertools 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

  • Dependency clap 2.24.2 is outdated

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

    clap versions

• pafe-sys

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

  • Incorrect category

    Crate's categories property in Cargo.toml contains 'smartcard', which isn't a category we recognize

    lib.rs has simplified and merged some of crates.io categories. Please file a bug if we got it wrong.

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["smart-card", "libpafe", "smartcard"] (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.

• pafe, pafe-sys

  • Latest stable release is old

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

• sega_film

  • Could not fetch repository

    We've had trouble cloning git repo from https://github\.com/mistydemeo/sega\_film\.git

• sega_cmp

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["compression", "sega", "data-format", "cmp", "header"] (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.

• dist

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