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.

• vtkio

  • Dependency quick-xml ^0.36 is significantly outdated

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

    quick-xml versions

  • Dependency base64 ^0.22 is a bit outdated

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

    base64 versions

  • Dependency lz4_flex ^0.11 is outdated

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

    lz4_flex versions

  • Dependency num-derive ^0.4 is a bit outdated

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

    num-derive versions

  • Dependency trim-in-place ^0.1 is slightly outdated

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

    trim-in-place versions

  • Latest prerelease is old

    It's been over 4 months. 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").

    Users pay attention to the latest release date. Even if the crate is perfectly fine as-is, users may not know that.

    Maintenance status field docs

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["parser-implementations"] 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 'flate2' 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 'flate2', 'rayon', 'quick-xml', 'serde', 'xz2', 'tokio', 'lz4' may have been unintentional.

    Crate features

• geometry-predicates

  • Latest stable release is old

    It's been over 5 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").

    If the crate is truly stable, why not make a 1.0.0 release?

    Maintenance status field docs

• cargo-hdk

  • Dependency cargo_metadata ^0.15 is significantly outdated

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

    cargo_metadata versions

  • Dependency clap ^3 is significantly outdated

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

    clap versions

  • Dependency clap-verbosity-flag ^1 is significantly outdated

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

    clap-verbosity-flag versions

  • Dependency env_logger ^0.9 is significantly outdated

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

    env_logger versions

  • Dependency terminal_size ^0.2 is significantly outdated

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

    terminal_size versions

  • Imprecise dependency requirement anyhow = ^1

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

    anyhow versions

  • Dependency colored ^2 is outdated

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

    colored versions

  • Latest stable release is old

    It's been over 3 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").

    Maintenance status field docs

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["development-tools::cargo-plugins"] to the Cargo.toml.

    List of available categories

• ipopt-sys

  • Missing categories

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

    List of available categories

  • Dependency bindgen ^0.71 is significantly outdated

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

    bindgen versions

  • Dependency rust-crypto ^0.2 has issues

    It may not be actively developed any more. Consider changing the dependency.

    rust-crypto crate

  • Published crate doesn't match its repository

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

    Looked for the crate in ipopt-sys/. Fetched https://github.com/elrnv/ipopt-rs.git 76cea034f688f3ef0d61797ff2da8d566bd22966.

    Checked on 2024-12-15

    This check is experimental.

    Forum thread

  • *-sys crate without links property

    If this crate uses C libraries with public symbols, consider adding links = "ipopt" 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.

  • Imprecise dependency requirement lazy_static = ^1

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

    lazy_static versions

• lsn

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

  • README missing from the repository

    We've searched https://github\.com/elrnv/lsn\.git and could not find a README file there.

  • README missing from crate tarball

    Cargo sometimes fails to package the README file. Ensure the path to the README in Cargo.toml is valid, and points to a file inside the crate's directory.

  • Dependency colored ^2.0.4 is outdated

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

    colored versions

  • Imprecise dependency requirement clap = ^4

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

    clap versions

  • Missing categories

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

    List of available categories

• autodiff

  • Dependency nalgebra ^0.32 is outdated

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

    nalgebra versions

  • Dependency simba ^0.8 is outdated

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

    simba versions

  • Imprecise dependency requirement bytemuck = ^1

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

    bytemuck versions

  • Latest stable release is old

    It's been over 3 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").

    Maintenance status field docs

  • Missing categories

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

    List of available categories

• ipopt

  • Published crate doesn't match its repository

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

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

    • Cargo.lock not found.

    Fetched https://github.com/elrnv/ipopt-rs.git 76cea034f688f3ef0d61797ff2da8d566bd22966.

    Checked on 2024-12-15

    Forum thread

  • Missing categories

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

    List of available categories

• reinterpret

  • Latest stable release is old

    It's been over 6 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").

    Maintenance status field docs

• flatk

  • Latest stable release is old

    It's been over 4 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").

    Maintenance status field docs

• flatk, reinterpret, data-buffer

  • Missing categories

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

    List of available categories

• dync

  • Missing categories

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

    List of available categories

• data-buffer

  • Latest stable release is old

    It's been over 6 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").

    Maintenance status field docs

• hrbf

  • Missing categories

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

    List of available categories

  • Dependency nalgebra ^0.32 is outdated

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

    nalgebra versions

• accelerate-framework

  • 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

• unroll, flatk-derive, dync-derive, gut-derive, meshx-derive

  • Dependency syn ^1.0 is significantly outdated

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

    syn versions

• accelerate-sys

  • Dependency bindgen ^0.69 is significantly outdated

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

    bindgen versions

  • 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

• flatk-derive

  • Could not fetch repository

    We've had trouble cloning git repo from https://github\.com/elrnv/flatk\-derive\.git

    At the moment we only support git, and attempt fetching when we index a new release. Cloning is necessary for lib.rs to gather data that is missing on crates.io, e.g. to correctly resolve relative URLs in README files, which depend on repository layout and non-standard URL schemes of repository hosts.

  • Dependency proc-macro-crate ^1.0 is significantly outdated

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

    proc-macro-crate versions

  • README missing from crate tarball

    Cargo sometimes fails to package the README file. Ensure the path to the README in Cargo.toml is valid, and points to a file inside the crate's directory.

  • Imprecise dependency requirement lazy_static = ^1

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

    lazy_static versions

  • Latest stable release is old

    It's been over 5 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").

    Maintenance status field docs

• dync-derive

  • Dependency heck ^0.3 is significantly outdated

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

    heck versions

  • Latest stable release is old

    It's been over 6 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").

    Maintenance status field docs

• gut-derive

  • Latest stable release is old

    It's been over 6 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").

    Maintenance status field docs

• meshx-derive

  • Latest stable release is old

    It's been over 4 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").

    Maintenance status field docs

• gltfgen

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/gltfgen ) failed. Please try again later.

• meshx

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/meshx ) failed. Please try again later.

• gut

  • Internal error

    We couldn't check this crate at this time, because: timed out validating Origin( lib.rs/crates/gut ). Please try again later.

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