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.

• checs

  • Failed to verify create's content against its repository

    Verified 6 out of 17 files (includes 3 Cargo-generated).

    • warning: Crate tarball has been published from the commit 473dbcaf731a4f969387a60dbb08b0b5584bd3ee, 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: 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.
    • README.md does not match the repository.
    • Cargo.toml.orig does not match the repository.
    • basic.rs does not match the repository.
    • src/
      • lib.rs does not match the repository.
      • iter.rs does not match the repository.
      • sparse.rs does not match the repository.
      • world.rs does not match the repository.
      • component.rs does not match the repository.
      • intersect.rs does not match the repository.
      • entity.rs does not match the repository.
      • query.rs does not match the repository.

    Fetched https://codeberg.org/tinturing/checs 681c43ea2b6bc7e19a65193c4edef1777e035378.

    Checked on 2025-03-30

    This check is experimental.

    Forum thread

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

    Crate features

• lb

  • Dependency termion 2.0.1 is significantly outdated

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

    termion versions

  • Published crate doesn't match its repository

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

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

    • Cargo.lock not found.

    Fetched https://codeberg.org/tinturing/lb 765a89349009fa101b71e010a615e810620ab132.

    Checked on 2024-10-04

    Forum thread

  • Dependency image 0.24.5 is outdated

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

    image versions

• checs_proc

  • Failed to verify create's content against its repository

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

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

    Looked for the crate in checs_proc/. Fetched https://codeberg.org/tinturing/checs tagged v0.4.0 (f3ea149bb5029c5d2212026a7964366114c46c6e).

    Checked on 2025-04-09

    Forum thread

• checs_proc, ch, pound

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

• ch

  • Crate contains junk files

    The crate contains boilerplate Rust files with no real functionality.

• pound

  • Crate contains junk files

    The crate contains boilerplate Rust files with no real functionality.

No issues found in: chron

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