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.

• airshipper

  • Dependency iced 0.12.1 is significantly outdated

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

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

    iced versions

  • Dependency pulldown-cmark 0.12.2 is significantly outdated

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

    pulldown-cmark versions

  • Dependency bytesize 1.0.1 is slightly outdated

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

    Easy way to bump dependencies: cargo install cargo-edit; cargo upgrade -i; Also check out Dependabot service on GitHub.

    bytesize versions

  • Dependency colored 2.0 is a bit outdated

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

    colored versions

  • Dependency derive_more 1.0.0 is outdated

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

    derive_more versions

  • Dependency html2text 0.13 is outdated

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

    html2text versions

  • Dependency rand 0.8.5 is a bit outdated

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

    rand versions

  • Dependency ron 0.8.1 is outdated

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

    ron versions

  • Dependency self_update 0.41.0 is outdated

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

    self_update versions

  • Failed to verify create's content against its repository

    Verified 66 out of 93 files (includes 3 Cargo-generated).

    • warning: Crate tarball has been published from a different commit than the commit tagged by git tag 'v0.16.0'.
      • Create git tags after comitting any changes, and commit changes after bumping versions and running cargo update.

    Files in the crates.io crate compared to the repository:

    • Cargo.lock not found.
    • net.veloren.airshipper.png does not match the repository.
    • assets/fonts/
      • Poppins-Medium.ttf does not match the repository.
      • Poppins-Light.ttf does not match the repository.
      • Poppins-Bold.ttf does not match the repository.
      • Poppins-Regular.ttf does not match the repository.
    • assets/icons/
      • book.png does not match the repository.
      • key.png does not match the repository.
      • ping1.png does not match the repository.
      • ping_error.png does not match the repository.
      • globe.png does not match the repository.
      • ping2.png does not match the repository.
      • up_right_arrow.png does not match the repository.
      • chat.png does not match the repository.
      • ping_none.png does not match the repository.
      • ping4.png does not match the repository.
      • user.png does not match the repository.
      • download.png does not match the repository.
      • folder.png does not match the repository.
      • heart.png does not match the repository.
      • ping3.png does not match the repository.
      • settings.png does not match the repository.
      • star.png does not match the repository.
      • changelog.png does not match the repository.
    • veloren-logo.png does not match the repository.
    • banner.bmp does not match the repository.
    • wix/
      • Banner.bmp does not match the repository.
      • Dialog.bmp does not match the repository.

    Looked for the crate in client/. Fetched https://gitlab.com/veloren/airshipper.git a0b49d792a2807338fec7d675da1630749d71c0c.

    Checked on 2025-03-30

    This check is experimental.

    Forum thread

  • Imprecise dependency requirement bytes = 1

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

    bytes versions

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["text-processing"] 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 = ["airshipper", "download", "log-file", "user", "airshipper-server"] (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.

  • Optional dependency 'openssl-sys' exposed as an implicit feature

    Cargo automatically makes publicly-available crate features for every optional dependency, unless the dependencies are referenced using dep: syntax. Feature 'openssl-sys' may have been unintentional.

    Crate features

• vui, bauble_macros, bauble

  • Crate contains junk files

    The crate contains boilerplate Rust files with no real functionality.

• bauble_macros

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