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.

• ort_custom_op

  • Dependency ndarray 0.15 is outdated

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

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

    ndarray versions

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["science::ml"] 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 = ["operator", "onnx-runtime", "abstraction", "interfacing", "framework"] (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.

  • No readme property

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

• root-io

  • Dependency lzma-rs 0.1.1 is significantly outdated

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

    lzma-rs versions

  • Dependency nom ^5 is significantly outdated

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

    nom versions

  • Dependency quote 0.3.15 is significantly outdated

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

    quote versions

  • Dependency reqwest 0.10 is significantly outdated

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

    reqwest versions

  • Dependency uuid 0.8.2 is significantly outdated

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

    uuid versions

  • Dependency bitflags 1.0.0 is outdated

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

    bitflags versions

  • Imprecise dependency requirement flate2 = ^1

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

    flate2 versions

• malice

  • Dependency alice-sys 0.1.1 has issues

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

    alice-sys crate

  • Dependency itertools 0.8.1 is significantly outdated

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

    itertools versions

  • Dependency nom ^5 is significantly outdated

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

    nom versions

  • Dependency tokio 0.2 has issues

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

    tokio crate

  • Dependency bitflags 1.0.1 is outdated

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

    bitflags versions

• cargo-with

  • Dependency env_logger 0.6.0 is significantly outdated

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

    env_logger versions

  • Dependency failure 0.1.3 has issues

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

    failure crate

  • Dependency clap 2.32 is outdated

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

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

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

    Maintenance status field docs

• root-ls

  • Dependency rustfmt 0.9.0 has issues

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

    rustfmt crate

  • Dependency tokio 0.2 has issues

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

    tokio crate

  • Dependency clap ^2 is outdated

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

    clap versions

  • Imprecise dependency requirement clap = ^2

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

• alice-open-data

  • Dependency failure 0.1.1 has issues

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

    failure crate

  • Dependency glob ^0.2.11 is significantly outdated

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

    glob versions

  • Dependency reqwest 0.10 is significantly outdated

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

    reqwest versions

  • Dependency dirs 1.0 is outdated

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

    dirs versions

• malice, root-io, root-ls, alice-download

  • Dependency failure 0.1.5 has issues

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

    failure crate

• alice-download

  • Dependency indicatif ^0.6.0 is significantly outdated

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

    indicatif versions

  • Dependency tokio 0.2.9 has issues

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

    tokio crate

  • Dependency clap ^2 is outdated

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

    clap versions

  • Imprecise dependency requirement clap = ^2

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

• malice, root-io, root-ls, alice-open-data, alice-download

  • 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

• alice-sys

  • Dependency bindgen ^0.29.0 is significantly outdated

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

    bindgen versions

  • Dependency gcc 0.3 has issues

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

    gcc crate

  • 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

  • *-sys crate without links property

    If this crate uses C libraries with public symbols, consider adding links = "alice" 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 alice-open-data 0.1.0 is outdated

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

    alice-open-data 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

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