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.

• stomp-rs

  • 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 uuid 0.8 is significantly outdated

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

    uuid 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

• openapi-gateway

  • Missing categories

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

    List of available categories

  • Dependency axum 0.4 is significantly outdated

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

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

    axum versions

  • Dependency hyper-rustls 0.23 is significantly outdated

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

    hyper-rustls 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 serde = 1

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

    serde versions

  • Dependency base64 0.13 is outdated

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

    base64 versions

  • Dependency cron-parser 0.7 is outdated

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

    cron-parser versions

  • Dependency hyper 0.14 is outdated

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

    hyper versions

  • Dependency thiserror 1 is a bit outdated

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

    thiserror versions

  • Dependency toml 0.5 is outdated

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

    toml versions

  • Dependency tower 0.4 is outdated

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

    tower versions

  • Missing keywords

    Help users find your crates. Add keywords = ["api-gateway", "open-api", "routes", "hot-reloading", "specification"] (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.

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