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.

• futures-signals

  • Published crate doesn't match its repository

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

    Fetched https://github.com/pauan/rust-signals.git 9ba9e0accab33527217d9ddc4be741d6ad3b258d.

    Checked on 2024-07-28

    This check is experimental.

    Forum thread

• dominator

  • Dependency gloo-events 0.1.2 is outdated

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

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

    gloo-events versions

  • Failed to verify create's content against its repository

    Verified 19 out of 20 files (includes 2 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 '0.5.38'.
      • git tag v0.5.38 4959f3ced8015ec03ca520876a86a3dc0852c0b5; git push origin --tags

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

    • canvas_2d.rs not found.

    Fetched https://github.com/pauan/rust-dominator.git 4959f3ced8015ec03ca520876a86a3dc0852c0b5.

    Checked on 2025-04-29

    Forum thread

• discard

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

    It's an opportunity to update it to the current Rust edition.

    Maintenance status field docs

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