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.

• rustic_core

  • Dependency nix 0.30.1 is outdated

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

    nix versions

  • Dependency pariter 0.5.1 is slightly outdated

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

    pariter versions

  • Imprecise dependency requirement xattr = 1

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

    xattr versions

• rustic-rs

  • Dependency convert_case 0.9.0 is significantly outdated

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

    convert_case versions

  • Dependency self_update =0.39.0 is significantly outdated

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

    self_update versions

  • Dependency zip 6.0.0 is significantly outdated

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

    zip versions

  • Locked dependency version self_update =0.39.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.

    self_update versions

  • Published crate doesn't match its repository

    Verified 87 out of 88 files (includes 2 Cargo-generated).

    • error: Cargo.lock was suspiciously large.
      • If you don't need this file, use include or exclude in Cargo.toml, otherwise file a bug at https://gitlab.com/lib.rs/main

    Fetched https://github.com/rustic-rs/rustic.git tagged v0.10.3 (bc5c09c6531042824379e18554086958d565fd96).

    Checked on 2025-12-28

    This check is experimental.

    Forum thread

  • Dependency crossterm 0.28 is outdated

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

    crossterm versions

  • Dependency dav-server 0.8.0 is a bit outdated

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

    dav-server versions

  • Dependency ratatui 0.29.0 is outdated

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

    ratatui versions

  • Dependency reqwest 0.12.24 is outdated

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

    reqwest versions

  • Dependency warp 0.3.7 is a bit outdated

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

    warp versions

  • Imprecise dependency requirement aho-corasick = 1

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

    aho-corasick versions

• rustic_testing

  • No repository property

    Specify git repository URL in Cargo.toml to help users find more information, contribute, and for lib.rs to read more info.

  • No readme property

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

  • Imprecise dependency requirement rustic_core = 0

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

    rustic_core versions

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["development-tools::testing"] 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 = ["testing", "rustic", "rustic-rs", "rustic-testuing", "ecosystem"] (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.

• rustic_scheduler

  • Dependency cron 0.13.0 is significantly outdated

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

    cron versions

  • Dependency gethostname 0.5.0 is significantly outdated

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

    gethostname versions

  • Imprecise dependency requirement anyhow = 1

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

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

    abscissa_core versions

  • Dependency abscissa_tokio 0.8.0 is outdated

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

    abscissa_tokio versions

  • Dependency axum 0.7.9 is outdated

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

    axum versions

  • Dependency rustic_core 0.7.1 is outdated

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

    rustic_core versions

  • Dependency sailfish 0.9.0 is outdated

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

    sailfish versions

  • Dependency toml 0.8.19 is outdated

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

    toml versions

  • Dependency tungstenite 0.24.0 is outdated

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

    tungstenite versions

• rustic_server

  • Imprecise dependency requirement anyhow = 1

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

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

    abscissa_core versions

  • Dependency abscissa_tokio 0.8.0 is outdated

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

    abscissa_tokio versions

  • Dependency axum 0.7 is outdated

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

    axum versions

  • Dependency axum-auth 0.7 is outdated

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

    axum-auth versions

  • Dependency axum-extra 0.9 is outdated

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

    axum-extra versions

  • Dependency axum-macros 0.4 is outdated

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

    axum-macros versions

  • Dependency axum-range 0.4 is outdated

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

    axum-range versions

  • Dependency axum-server 0.7 is outdated

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

    axum-server versions

  • Dependency inquire 0.7 is outdated

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

    inquire versions

  • Dependency rand 0.8 is outdated

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

    rand versions

  • Dependency strum 0.26 is outdated

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

    strum versions

  • Dependency toml 0.8 is outdated

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

    toml versions

• rustic_backend

  • Dependency opendal 0.54.1 is outdated

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

    opendal versions

  • Dependency reqwest 0.12.24 is outdated

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

    reqwest versions

  • Imprecise dependency requirement rustic_core = 0

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

    rustic_core versions

• aes256ctr_poly1305aes

  • Dependency cipher 0.4 is a bit outdated

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

    cipher versions

  • Imprecise dependency requirement subtle = 2

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

    subtle versions

• rustic_web, rustic_auth, rustiq, rustic_daemon, rustic_plugins, rustic_store

  • Could not fetch repository

    We've had trouble cloning git repo from https://github\.com/rustic\-rs/rustic\.git

    At the moment we only support git, and attempt fetching when we index a new release. Cloning is necessary for lib.rs to gather data that is missing on crates.io, e.g. to correctly resolve relative URLs in README files, which depend on repository layout and non-standard URL schemes of repository hosts.

• rustic_web, rustic_cli, rustic_auth, rustiq, rustic_bench, rustic_daemon, rustic_plugins, rustic_store, rustic_ui

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

• rustic_web, rustic_cli, rustic_auth, rustiq, rustic_bench, rustic_daemon, rustic_plugins, rustic_store, rustic_ui

  • Crate contains junk files

    The crate contains boilerplate Rust files with no real functionality.

No issues found in: rustic_config

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