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.

• aur-depends

  • README missing from the repository

    We've searched https://github\.com/morganamilo/aur\-depends\.git and could not find a README file there.

  • Dependency srcinfo 1.3.1 is a bit outdated

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

    srcinfo versions

  • Failed to verify create's content against its repository

    Verified 14 out of 17 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 d8deb189dcdc54b6cb83457e59063b13052a1149, which is not in the repository.
      • Create git tags after comitting any changes, and commit changes after bumping versions and running cargo update.
    • warning: Found a Cargo.toml for this package in its repo (via tags), but the version was different.
      • Make sure to commit and tag after bumping the version number.
    • warning: Could not discover crate's location in its repository (via tags).
    • warning: There is no matching git tag containing version '4.0.5'.
    • 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.
    • src/
      • resolve.rs does not match the repository.
      • actions.rs does not match the repository.

    Fetched https://github.com/morganamilo/aur-depends.git a5bebaff560fc85d7ff38292e05d0ba8a4c84f79.

    Checked on 2025-10-11

    This check is experimental.

    Forum thread

• srcinfo

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

    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.

    serde versions

• pacmanconf

  • README missing from the repository

    We've searched https://github\.com/morganamilo/pacmanconf\.rs\.git and could not find a README file there.

  • Published crate doesn't match its repository

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

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

    • Cargo.lock not found.

    Looked for the crate in pacmanconf/. Fetched https://github.com/morganamilo/pacmanconf.rs.git 7965b49e7d91cca16c06238e44be96692050efd6.

    Checked on 2025-11-02

    Forum thread

• aur-fetch

  • README missing from the repository

    We've searched https://github\.com/morganamilo/aur\-fetch\.rs\.git and could not find a README file there.

  • Using outdated edition for no reason

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

• ably

  • Missing categories

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

  • Dependency block-modes 0.9.1 has issues

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

    block-modes crate

  • Dependency base64 0.13.0 is significantly outdated

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

    base64 versions

  • Dependency num-derive 0.3.3 is outdated

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

    num-derive versions

  • Dependency rand 0.8.5 is outdated

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

    rand versions

  • Dependency reqwest 0.11.10 is outdated

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

    reqwest versions

• cini

  • README missing from the repository

    We've searched https://github\.com/morganamilo/pacmanconf\.rs\.git and could not find a README file there.

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

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

    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

• aur-depends, pacmanconf, aur-fetch

  • No readme property

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

• alpm-sys

  • Dependency bindgen 0.70.0 is significantly outdated

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

    bindgen versions

  • Published crate doesn't match its repository

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

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

    • Cargo.lock not found.

    Looked for the crate in alpm-sys/. Fetched https://github.com/archlinux/alpm.rs.git b0a9e248ba117ea7ad56cc6ba273aaae570fdac6.

    Checked on 2025-05-11

    Forum thread

  • *-sys crate without links property

    If this crate uses C libraries with public symbols, consider adding links = "alpm" to crate's Cargo.toml to avoid other libraries colliding with them. Note that the links property adds exclusivity to dependency resolution, but doesn't do any linking.

    This is also needed to protect your crate from duplicate older versions of itself. C symbols are global, and duplicate symbols can cause all sorts of breakage.

  • Optional dependency 'bindgen' 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 'bindgen' may have been unintentional.

    Crate features

• aur-depends, paccat, alpm, aur-fetch, alpm-utils, raur, alpm-sys

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["os::unix-apis"] to the Cargo.toml.

    List of available categories

• alpm

  • Optional dependency 'libarchive' 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 'libarchive', 'libarchive3-sys' may have been unintentional.

    Crate features

• raur

  • Dependency reqwest 0.11.9 is outdated

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

    reqwest versions

  • Optional dependency 'async-trait' 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 'async-trait' may have been unintentional.

    Crate features

  • Using outdated edition for no reason

    We estimate that this crate requires at least Rust 1.62, which is newer than the last 2018-edition compiler. You can upgrade without breaking any compatibility. Run cargo fix --edition and update edition="…" in Cargo.toml.

    The Edition Guide

• raur-ext

  • README missing from the repository

    We've searched https://github\.com/morganamilo/raur\-ext\.git and could not find a README file there.

  • Dependency raur 3.0.1 is outdated

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

    raur versions

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["caching", "os::unix-apis"] to the Cargo.toml.

    List of available categories

• raur-ext, publish-testing, publish-testing5, vercmp, alpm-desc, publish-testing2, makepkg, publish-testing4, publish-testing3, alpm-dbinfo, libaur

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

• publish-testing, vercmp, alpm-desc, makepkg, publish-testing3, alpm-dbinfo, libaur

  • Crate contains junk files

    The crate contains boilerplate Rust files with no real functionality.

• publish-testing5, publish-testing2, publish-testing4

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

• libaur

  • README missing from the repository

    We've searched https://github\.com/morganamilo/libaur\.rs\.git and could not find a README file there.

• paru

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/paru ) failed. Please try again later.

No issues found in: pkgbuild alpm-sys-fork

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