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.

• fbws

  • Published crate doesn't match its repository

    Partially verified 9 files (includes 2 Cargo-generated).

    Fetched https://github.com/formerlybased/fbws.git 7b1a67a9e5ba85950680ae5917338544bc876ae3.

    Checked on 2024-08-10

    This check is experimental.

    Forum thread

  • Dependency config 0.13.3 is outdated

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

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

    config versions

  • Dependency hyper 0.14 is outdated

    Consider upgrading to 1.6.0 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.

    hyper versions

  • Imprecise dependency requirement tokio = 1

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

    tokio versions

  • Missing categories

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

No issues found in: formerlybased-web-server

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