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.

• log-analyzer-transient-types

  • README missing from the repository

    We've searched https://github\.com/markusgod/log\-analyzer\.git and could not find a README file there.

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

  • Missing keywords

    Help users find your crates. Add keywords = ["log-analyzer-transient-types", "shared", "serialization"] (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.

• log-analyzer-transient-types, another-mono-sys, log-analyzer-collector, log-analyzer-server

  • 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

• log-analyzer-server

  • README missing from the repository

    We've searched https://github\.com/markusgod/log\-analyzer\.git and could not find a README file there.

  • Dependency parking_lot 0.11 is significantly outdated

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

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

    parking_lot versions

  • Dependency serde_yaml 0.8 has issues

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

    serde_yaml crate

  • Dependency tantivy 0.14 is significantly outdated

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

    tantivy versions

  • Dependency tokio-util 0.6 is significantly outdated

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

    tokio-util versions

  • Dependency tracing-subscriber 0.2 is significantly outdated

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

    tracing-subscriber versions

  • 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

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

  • Dependency tokio-serde 0.8 is a bit outdated

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

    tokio-serde versions

  • Missing keywords

    Help users find your crates. Add keywords = ["index", "log", "stores", "data"] (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.

• log-analyzer-collector

  • Dependency tokio-util 0.6 is significantly outdated

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

    tokio-util versions

  • Dependency tracing-subscriber 0.2 is significantly outdated

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

    tracing-subscriber versions

  • Dependency notify 4 is outdated

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

    notify versions

  • Dependency tokio-serde 0.8 is a bit outdated

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

    tokio-serde versions

  • Dependency toml 0.5 is outdated

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

    toml versions

  • Imprecise dependency requirement tokio = 1

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

    Help users find your crates. Add keywords = ["server", "logging", "target", "back", "sends"] (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.

• another-mono-sys

  • Dependency bindgen 0.60.1 is significantly outdated

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

    bindgen versions

  • Missing keywords

    Help users find your crates. Add keywords = ["mono", "bindings", "bindgen", "mono-2-0", "docs"] (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.

  • 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

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