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.

• project_management

  • Published crate doesn't match its repository

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

    Fetched https://github.com/pbower/project_management.git cecfd9aaa744e374085194f6c4c44730d6c17c09.

    Checked on 2025-08-24

    This check is experimental.

    Forum thread

  • Dependency ratatui 0.29 is outdated

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

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

    ratatui versions

• simd-kernels, vec64, spacecell, dsa64, flatarrow, arrowmax

  • No repository property

    Specify git repository URL in Cargo.toml to help users find more information, contribute, and for lib.rs to read more info.

• minarrow-pyo3

  • Dependency pyo3 0.23 is significantly outdated

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

    pyo3 versions

  • Dependency pyo3-build-config 0.23 is significantly outdated

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

    pyo3-build-config versions

  • Imprecise dependency requirement thiserror = 2

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

    thiserror versions

  • *-sys crate without links property

    If this crate uses C libraries with public symbols, consider adding links = "minarrow-pyo3" to crate's Cargo.toml to avoid other libraries colliding with them. Note that the links property adds exclusivity to dependency resolution, but doesn't do any linking.

    This is also needed to protect your crate from duplicate older versions of itself. C symbols are global, and duplicate symbols can cause all sorts of breakage.

• lightstream

  • Dependency minarrow 0.9.1 is outdated

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

    minarrow versions

  • Dependency tokio-tungstenite 0.28 is outdated

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

    tokio-tungstenite versions

  • Imprecise dependency requirement tokio = 1

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

    tokio versions

  • Optional dependency 'snap' 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 'snap', 'libc', 'quinn', 'prost', 'rmp-serde', 'serde', 'tokio-tungstenite', 'wtransport' may have been unintentional.

    Crate features

• simd-kernels

  • Dependency minarrow 0.9.1 is outdated

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

    minarrow versions

  • Imprecise dependency requirement cc = 1

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

    cc versions

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["algorithms"] to the Cargo.toml.

    Even if there are no categories that fit precisely, pick one that is least bad. You can also propose new categories in crates.io issue tracker.

    List of available categories

  • Optional dependency 'blas-src' 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 'blas-src', 'openblas-src', 'blas', 'lapack', 'lapack-src' may have been unintentional.

    Crate features

• minarrow

  • *-sys crate without links property

    If this crate uses C libraries with public symbols, consider adding links = "minarrow" to crate's Cargo.toml to avoid other libraries colliding with them. Note that the links property adds exclusivity to dependency resolution, but doesn't do any linking.

  • Imprecise dependency requirement cc = 1

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

    cc versions

  • Optional dependency 'rayon' 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 'rayon', 'arrow', 'ryu', 'polars-arrow', 'arrow-schema', 'cc', 'memchr', 'polars' may have been unintentional.

    Crate features

  • Published crate contains binary files

    The crate contains binary files (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

• flatarrow

  • docs.rs build failed

    docs.rs site failed to build the crate, so users will have trouble finding the documentation. Docs.rs supports multiple platforms and custom configurations, so you can make the build work even if normal crate usage has special requirements.

    Docs.rs doesn't need to run or even link any code, so system dependencies can simply be skipped. You can also set cfg() flags just for docs.rs and use them to hide problematic code.

    Detecting docs.rs

  • Dependency lightstream 0.3.0 is outdated

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

    lightstream versions

  • Dependency minarrow 0.7.2 is outdated

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

    minarrow versions

• vec64

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["hardware-support", "caching"] to the Cargo.toml.

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["simd", "simd-alignment", "64-byte", "vec", "automatic"] (up to 5) to the Cargo.toml. Best keywords are alternative terms or their spellings that aren't in the name or description. Also add a keyword that precisely categorizes this crate and groups it with other similar crates.

  • Optional dependency 'rayon' 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 'rayon', 'wasm-bindgen-rayon', 'wasm-bindgen' may have been unintentional.

    Crate features

• terminal_tools

  • Dependency ratatui 0.29 is outdated

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

    ratatui versions

  • Dependency viuer 0.9 is outdated

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

    viuer versions

• dsa64

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["data-structures"] to the Cargo.toml.

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["high-performance-computing", "data-structures", "alignment", "64-byte", "backed"] (up to 5) to the Cargo.toml. Best keywords are alternative terms or their spellings that aren't in the name or description. Also add a keyword that precisely categorizes this crate and groups it with other similar crates.

• arrowmax

  • docs.rs build failed

    docs.rs site failed to build the crate, so users will have trouble finding the documentation. Docs.rs supports multiple platforms and custom configurations, so you can make the build work even if normal crate usage has special requirements.

    Detecting docs.rs

  • Dependency lightstream 0.3.0 is outdated

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

    lightstream versions

  • Dependency minarrow 0.7.2 is outdated

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

    minarrow versions

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