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.

• raptor-code

  • Published crate doesn't match its repository

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

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

    • Cargo.lock not found.

    Fetched https://github.com/ypo/raptor.git ea8c404879d2ce8b5b33dcb16e0526bc30d23eb7.

    Checked on 2025-02-16

    This check is experimental.

    Forum thread

  • Dependency criterion 0.5 is outdated

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

    criterion versions

• flute

  • Dependency pyo3 0.24 is outdated

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

    pyo3 versions

  • Imprecise dependency requirement utoipa = 5

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

    utoipa versions

  • Optional dependency 'pyo3-log' 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 'pyo3-log', 'utoipa', 'opentelemetry-semantic-conventions', 'pyo3', 'opentelemetry' may have been unintentional.

    Crate features

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