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.

• rustedbytes-counterlines

  • Dependency toml 0.9.5 is significantly outdated

    Consider upgrading to 1.1.0+spec-1.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.

    toml versions

  • Dependency sha2 0.10 is a bit outdated

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

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

    sha2 versions

  • Failed to verify create's content against its repository

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

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

    Fetched https://github.com/mad4j/rustedbytes-counterlines.git fbdae737eeef8cd8afd6373c964e7244d8281841.

    Checked on 2025-08-17

    This check is experimental.

    Forum thread

• uuidrs

  • Dependency structopt 0.3.25 has issues

    It has been losing active users, which may be a sign it's deprecated or obsolete. Consider replacing it with a different crate.

    structopt crate

  • Dependency rand 0.8.4 is outdated

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

    rand versions

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

    If the crate is truly stable, why not make a 1.0.0 release?

    Maintenance status field docs

• rustedbytes-bytepusher

  • Dependency rodio 0.20.1 is outdated

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

    rodio versions

  • Failed to verify create's content against its repository

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

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

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

    • Cargo.lock not found.

    Fetched https://github.com/mad4j/rustedbytes-bytepusher.git 0cd725d6a4d18483a71d1347439433216e3fd3ec.

    Checked on 2025-10-11

    Forum thread

• rustedbytes-randstuff

  • Dependency rand 0.8 is outdated

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

    rand versions

• intpackit

  • Incorrect category

    Crate's categories property in Cargo.toml contains 'integer-manipulation-library', 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

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

    Maintenance status field docs

• rustedbytes-tris

  • Internal error

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

• rustedbytes-pi

  • Internal error

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

No issues found in: rustedbytes-nmea datetag howlast rustedbytes-mandelbrot

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