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.

• directories

  • Failed to verify create's content against its repository

    Verified 14 out of 15 files (includes 3 Cargo-generated).

    • warning: The crates.io package has no information about its path inside its repository.
    • warning: Crate tarball has been published from the commit 7ff1b6d3222e752c76d0e9aa786b399f620320af, which is not in the repository.
      • Create git tags after comitting any changes, and commit changes after bumping versions and running cargo update.
    • warning: There is no matching git tag containing version '6.0.0'.
    • 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:

    • Cargo.lock not found.
    • Cargo.toml.orig does not match the repository.

    Fetched https://github.com/dirs-dev/directories-rs.git 4d76f1a5a0a979de3cac4c1ffb53c8b5a6f481a7.

    Checked on 2025-04-27

    This check is experimental.

    Forum thread

• directories, dirs, dirs-cli

  • Missing categories

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

• dirs-sys

  • Published crate doesn't match its repository

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

    Fetched https://github.com/dirs-dev/dirs-sys-rs.git 8bcd4aa2c35990d57a2cff2953793525fc42709c.

    Checked on 2025-01-12

    Forum thread

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["directory", "system-level", "helper", "known-folders"] (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.

  • Using outdated edition for no reason

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

• dirs

  • Failed to verify create's content against its repository

    Partially verified 14 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 '6.0.0'.
      • git tag v6.0.0 00511bdc252f491a72ac89f6d6a2463406266fb2; git push origin --tags

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

    • Cargo.lock not found.

    Fetched https://github.com/dirs-dev/dirs-rs.git 00511bdc252f491a72ac89f6d6a2463406266fb2.

    Checked on 2025-01-19

    Forum thread

• dirs-cli

  • Dependency windows-sys 0.48.0 is significantly outdated

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

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

    windows-sys versions

  • Dependency dirs 5.0.1 is outdated

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

    dirs versions

  • Using outdated edition for no reason

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

    The Edition Guide

• option-ext

  • Missing keywords

    Help users find your crates. Add keywords = ["extend", "replace", "operation", "methods"] (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.

• result-ext

  • Missing keywords

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

  • Using outdated edition for no reason

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

    The Edition Guide

• core-runtime

  • Missing categories

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

    List of available categories

  • Missing keywords

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

• core-compiler, core-runtime, core-parser, core-lang

  • 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

• core-compiler

  • Missing keywords

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

• core-compiler, core-parser, core-lang

  • Missing categories

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

    List of available categories

• core-compiler, core-runtime, core-parser, core-lang

  • 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

• core-parser

  • Missing keywords

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

• core-lang

  • Missing keywords

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

• soc, settings, paths

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

• soc, settings, paths

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