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.

• cargo-travis-fork

  • Dependency docopt 1.0 has issues

    It has been losing active users, which may be a sign it's deprecated or obsolete. Consider replacing it with a different crate.

    docopt crate

  • Dependency cargo 0.35 is significantly outdated

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

    cargo versions

  • Dependency failure 0.1 has issues

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

    failure crate

  • Dependency fs_extra =1.1.0 is significantly outdated

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

    fs_extra versions

  • Locked dependency version fs_extra =1.1.0

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    fs_extra versions

  • Imprecise dependency requirement badge = 0

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

    badge 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

  • Missing categories

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

  • Using outdated edition for no reason

    We estimate that this crate requires at least Rust 1.46, which is newer than the last 2015-edition compiler. You can upgrade without breaking any compatibility. Run cargo fix --edition and update edition="…" in Cargo.toml.

    Using the latest edition helps avoid old quirks of the compiler, and ensures Rust code has consistent syntax and behavior across all projects.

    The Edition Guide

• bevy_assets_bundler

  • Dependency bevy 0.10 is significantly outdated

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

    bevy versions

  • Dependency block-modes 0.8 has issues

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

    block-modes crate

  • Imprecise dependency requirement anyhow = 1

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

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

    aes versions

  • Dependency bs58 0.4 is outdated

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

    bs58 versions

  • Optional dependency 'aes' 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 'aes', 'block-modes' may have been unintentional.

    Crate features

• ru_annoy

  • Imprecise dependency requirement hashbrown = 0

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

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

    Maintenance status field docs

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["ru-annoy", "annoy", "dotnet", "nearest-neighbor", "approximate-knn"] (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.

• annoy-rs

  • Imprecise dependency requirement hashbrown = 0

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

    hashbrown 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 = ["hardware-support"] to the Cargo.toml.

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["annoy", "dotnet", "index", "nearest-neighbor", "dart"] (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.

• variant-config

  • Dependency ahash 0.7 has issues

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

    ahash crate

  • Dependency cranelift 0.80 is significantly outdated

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

    cranelift versions

  • Dependency cranelift-jit 0.80 is significantly outdated

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

    cranelift-jit versions

  • Dependency cranelift-module 0.80 is significantly outdated

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

    cranelift-module versions

  • Dependency serde_yaml 0.8 has issues

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

    serde_yaml crate

  • Imprecise dependency requirement anyhow = 1

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

    anyhow versions

  • Dependency hashbrown 0.12 is outdated

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

    hashbrown versions

  • Dependency toml 0.5 is outdated

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

    toml 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 = ["parser-implementations"] to the Cargo.toml.

    List of available categories

  • Missing keywords

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

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

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