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.

• py-rs

  • Published crate doesn't match its repository

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

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

    • Cargo.lock not found.

    Looked for the crate in py-rs/. Fetched https://github.com/blue-chestnut/py-rs.git 73654845a19b4fc728198865359e80980777c157.

    Checked on 2025-03-02

    This check is experimental.

    Forum thread

  • Dependency dprint-plugin-typescript 0.90 is outdated

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

    dprint-plugin-typescript versions

  • Dependency ordered-float >= 3, < 5 is outdated

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

    ordered-float versions

  • Imprecise dependency requirement bson = 2

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

    If you want to keep using truly minimal dependency requirements, please make sure you test them in CI with -Z minimal-versions Cargo option, because it's very easy to accidentally use a feature added in a later version.

    bson versions

  • Optional dependency 'uuid' 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 'uuid', 'bigdecimal', 'tokio', 'chrono', 'ordered-float', 'serde_json', 'bson', 'indexmap', 'dprint-plugin-typescript', 'bytes', 'url', 'heapless', 'semver', 'smol_str' may have been unintentional.

    Crate features

• py-rs-macros

  • Published crate doesn't match its repository

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

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

    • Cargo.lock not found.

    Looked for the crate in macros/. Fetched https://github.com/blue-chestnut/py-rs.git 73654845a19b4fc728198865359e80980777c157.

    Checked on 2025-03-02

    Forum thread

  • Imprecise dependency requirement termcolor = 1

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

    termcolor versions

  • No readme property

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

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