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.

• imagepipe

  • Dependency serde_yaml 0.8 has issues

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

    serde_yaml crate

  • Dependency image 0.24 is outdated

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

    image versions

  • Imprecise dependency requirement blake3 = 1

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

    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.

    blake3 versions

  • Missing keywords

    Help users find your crates. Add keywords = ["image-processing", "pipeline", "raw", "output-image", "camera"] (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.

• chimper

  • Dependency conrod_core 0.73 is significantly outdated

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

    conrod_core versions

  • Dependency conrod_winit 0.73 is significantly outdated

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

    conrod_winit versions

  • Dependency env_logger 0.8 is significantly outdated

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

    env_logger versions

  • Dependency glium 0.28 is significantly outdated

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

    glium versions

  • Dependency imagepipe 0.4 is significantly outdated

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

    imagepipe versions

  • Dependency winit 0.23 is significantly outdated

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

    winit versions

  • Dependency conrod_glium 0.73 is outdated

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

    conrod_glium versions

  • Dependency image 0.23 is outdated

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

    image versions

  • Dependency rand 0.8 is a bit outdated

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

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

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

    Maintenance status field docs

  • Missing keywords

    Help users find your crates. Add keywords = ["image-viewer", "graphical", "directory", "sorts", "browses"] (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.

• syncer

  • Dependency base64 0.9 is significantly outdated

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

    base64 versions

  • Dependency blake2 0.7.0 is significantly outdated

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

    blake2 versions

  • Dependency crossbeam 0.3.2 is significantly outdated

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

    crossbeam versions

  • Dependency hex 0.3.1 is significantly outdated

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

    hex versions

  • Dependency rand 0.4 is significantly outdated

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

    rand versions

  • Dependency rusqlite 0.13.0 is significantly outdated

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

    rusqlite versions

  • Dependency time 0.1.39 is significantly outdated

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

    time versions

  • Dependency toml 0.4 is significantly outdated

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

    toml versions

  • Dependency users 0.6.0 is significantly outdated

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

    users versions

  • Imprecise dependency requirement serde = 1

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

    serde versions

  • Latest stable release is old

    It's been over 7 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

  • The Cargo package has no git commit information

    Before publishing a package, make sure all packaged files are committed to the repository, and there are no "dirty" files. Push this commit to crate's public repository.

    To protect against supply chain attacks similar to CVE-2024-3094, lib.rs will soon start flagging non-reproducible packages without public source code as suspicious. Currently only git repositories are supported (but may be hosted anywhere, not just GitHub). If you'd like a different SCM supported, please file a feature request.

    More info

  • Dependency fuse_mt 0.4.3 is outdated

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

    fuse_mt versions

  • Missing keywords

    Help users find your crates. Add keywords = ["cache", "recently", "local", "locally", "filesystem"] (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.

• rawloader

  • Dependency toml 0.5 is outdated

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

    toml versions

  • Imprecise dependency requirement byteorder = 1

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

    byteorder versions

  • Missing keywords

    Help users find your crates. Add keywords = ["camera-image", "raw", "color-space", "extract", "digital"] (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.

• multicache

  • 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 = ["caching"] 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 = ["lru-cache", "thread-safe", "size", "weight", "arc"] (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.

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