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.

• resolvo

  • Could not find the crate in the repository

    Make sure the main branch of https://github\.com/prefix\-dev/resolvo contains the Cargo.toml for the crate. If you have forked the crate, change the repository property in Cargo.toml to your fork's URL.

  • Dependency async-std 1.13 has issues

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

    async-std crate

  • Dependency petgraph 0.7.1 is significantly outdated

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

    petgraph versions

  • Imprecise dependency requirement indexmap = 2

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

    indexmap versions

  • Optional dependency 'tabwriter' 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 'tabwriter', 'human_bytes' may have been unintentional.

    Crate features

• rattler_installs_packages

  • Dependency async_zip 0.0.16 is significantly outdated

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

    async_zip versions

  • Dependency fs4 0.8.2 is significantly outdated

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

    fs4 versions

  • Dependency itertools 0.12.1 is significantly outdated

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

    itertools versions

  • Dependency which 6.0.1 is significantly outdated

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

    which 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 fs-err 2.11.0 is a bit outdated

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

    fs-err versions

  • Dependency pep440_rs 0.4.0 is outdated

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

    pep440_rs versions

  • Dependency pep508_rs 0.3.0 is outdated

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

    pep508_rs versions

  • Dependency pyproject-toml 0.9.0 is outdated

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

    pyproject-toml versions

  • Dependency rattler_digest 0.19.3 is outdated

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

    rattler_digest versions

  • Dependency resolvo 0.4.0 is outdated

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

    resolvo versions

  • Dependency thiserror 1.0.58 is a bit outdated

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

    thiserror versions

  • Dependency zip 0.6.6 is outdated

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

    zip versions

  • Missing keywords

    Help users find your crates. Add keywords = ["rattler", "package", "archive", "resolving", "detail"] (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 (DOS exe). 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

• rusty-x

  • Dependency docopt 1 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

  • Missing categories

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

  • Dependency ansi_term 0.11.0 has issues

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

    ansi_term crate

  • Dependency colored 1.6 is significantly outdated

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

    colored versions

  • Dependency markdown 0.2 is significantly outdated

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

    markdown versions

  • Dependency skim 0.6.8 is significantly outdated

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

    skim versions

  • Dependency toml 0.4 is significantly outdated

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

    toml versions

  • Dependency dirs 1.0.3 is outdated

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

    dirs versions

  • Dependency prettyprint 0.3.0 is outdated

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

    prettyprint versions

  • Imprecise dependency requirement docopt = 1

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

    docopt 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

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