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.

• jpegxl-src

  • Published crate doesn't match its repository

    Verified 7 out of 8 files (includes 2 Cargo-generated).

    • error: Git repository error Odb/NotFound
      • Ooops? If this shouldn't happen, file a bug https://gitlab.com/lib.rs/main
    • error: object not found - no match for id (794a5dcf0d54f9f0b20d288a12e87afb91d20dfc); class=Odb (9); code=NotFound (-3)

    Looked for the crate in jpegxl-src/. Fetched https://github.com/inflation/jpegxl-rs.git tagged jpegxl-src-v0.11.2 (c609dcde9a612bbcdd9cea279c1c588c31720373).

    Fetched submodule jpegxl-src/libjxl from https://github.com/libjxl/libjxl.git 794a5dcf0d54f9f0b20d288a12e87afb91d20dfc.

    Checked on 2025-01-05

    This check is experimental.

    Forum thread

  • *-sys crate without links property

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

  • Missing categories

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

  • Missing keywords

    Help users find your crates. Add keywords = ["jpegxl", "jpegxl-src", "src"] (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

• vapoursynth4-rs

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["video-processing", "vapour-synth", "api", "api-version"] (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.

• vapoursynth4-rs-macros

  • README missing from the repository

    We've searched https://github\.com/inflation/vapoursynth4\-rs\.git and could not find a README file there.

  • No readme property

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

  • Dependency vapoursynth4-sys 0.2.0 is outdated

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

    vapoursynth4-sys versions

• inet-aton

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["inet-aton", "aton", "inet", "address"] (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.

• jpegxl-sys

  • Optional dependency 'jpegxl-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. Feature 'jpegxl-src' may have been unintentional.

    Crate features

• vapoursynth4-sys

  • *-sys crate without links property

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

• x265-sys

  • Dependency bindgen 0.51.0 is significantly outdated

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

    bindgen versions

  • *-sys crate without links property

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

  • 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

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["x265-sys", "h265", "x265"] (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.

  • 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

No issues found in: jpegxl-rs

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