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.

• libryzenadj

  • Dependency num_enum 0.6.1 is significantly outdated

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

    num_enum versions

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

    Fetched https://gitlab.com/dragonn/libryzenadj-rs.git 7662161262691a96e3bbab43eb01fb5a10c1a61c.

    Checked on 2024-10-28

    This check is experimental.

    Forum thread

  • Dependency thiserror 1.0.35 is a bit outdated

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

    thiserror versions

• libryzenadj-sys

  • Published crate doesn't match its repository

    Verified 38 out of 39 files (includes 2 Cargo-generated).

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

    • CMakeLists.txt does not match the repository.

    Looked for the crate in libryzenadj-sys/. Fetched https://gitlab.com/dragonn/libryzenadj-rs.git 7662161262691a96e3bbab43eb01fb5a10c1a61c.

    Fetched submodule libryzenadj-sys/RyzenAdj from https://github.com/flygoat/ryzenadj.git 50f53c7320cd922f0b5833fe7a7ec899d9d87eb1.

    Checked on 2025-04-29

    Forum thread

  • Dependency bindgen 0.69.4 is outdated

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

    bindgen versions

  • Published crate contains binary files

    The crate contains binary files (DOS exe, Windows DLL, static library). Crates are meant to be compiled from source. Please check that you haven't published temporary build files by accident. If you have test fixtures, consider excluding them from crates-io tarball, since Cargo doesn't run tests from crates-io packages.

    Audit page

• sea-orm-try-into-active-model

  • Published crate doesn't match its repository

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

    Fetched https://gitlab.com/dragonn/sea_orm_try_into_active_model.git 77be3ac56e317c0f5a0e9b8f965698d700a8203a.

    Checked on 2024-08-10

    Forum thread

  • Dependency sea-orm 0.12.1 is outdated

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

    sea-orm versions

  • Dependency sea-query 0.30.2 is outdated

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

    sea-query versions

• sea-orm-verify, sea-orm-try-into-active-model-macro

  • Dependency heck 0.4 is outdated

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

    heck versions

• sea-orm-try-into-active-model-macro

  • Imprecise dependency requirement syn = 2

    Cargo does not always pick latest versions of dependencies! Specify the version as syn = "2.0.101". 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.

    syn versions

  • Published crate doesn't match its repository

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

    Looked for the crate in sea-orm-try-into-active-model-macro/. Fetched https://gitlab.com/dragonn/sea_orm_try_into_active_model.git ee931ec8d105515bae27302c6a33c58a44dcf83f.

    Checked on 2024-07-24

    Forum thread

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