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.

• openexr

  • Dependency glam ^0.17 is significantly outdated

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

    glam versions

  • Dependency half ^1.7 is significantly outdated

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

    half versions

  • Dependency nalgebra ^0.27 is significantly outdated

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

    nalgebra versions

  • Dependency nalgebra-glm ^0.12 is significantly outdated

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

    nalgebra-glm 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.

    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 bitflags ^1.2 is outdated

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

    bitflags versions

  • Dependency imath-traits ^0.4 is slightly outdated

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

    imath-traits versions

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

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

    Maintenance status field docs

• usd

  • Dependency half ^1.6.0 is significantly outdated

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

    half 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

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["rendering::graphics-api"] 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

• openexr, ptex

  • Dependency thiserror ^1.0 is outdated

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

    thiserror versions

• openexr-sys

  • Missing categories

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

    List of available categories

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

  • *-sys crate without links property

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

  • Dependency cppmm-build ^0.2 is slightly outdated

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

    cppmm-build versions

  • Missing keywords

    Help users find your crates. Add keywords = ["github", "bindings", "vfx-rs", "ffi", "generated"] (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.

  • Published crate contains binary files

    The crate contains binary files (obscure autoconf code). 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

  • 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

• openvdb, materialx, seexpr, openshadinglanguage, opentimelineio, opencolorio, opensubdiv, openimageio

  • Crate contains junk files

    The crate contains boilerplate Rust files with no real functionality.

• alembic, openshadinglanguage-sys, opentimelineio-sys, openexr-core-sys, opensubdiv-sys, opencolorio-sys, openimageio-sys, materialx-sys, alembic-sys, seexpr-sys, usd-sys, openexr-core

  • Crate contains junk files

    The crate contains boilerplate Rust files with no real functionality.

No issues found in: ptex-sys

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