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.

• stat_common

  • Failed to verify create's content against its repository

    Verified 4 out of 6 files (includes 1 Cargo-generated).

    • warning: The crates.io package has no commit hash associated with it.
      • Publish a new version, without using --allow-dirty flag. Make sure all changes are committed before publishing. Use include/exclude in Cargo.toml to omit unnecessary files.
    • warning: There is no matching git tag containing version '1.1.4'.
    • warning: Had to perform fuzzy search of the head branch due to lack of commit information in the package.

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

    • Cargo.toml.orig does not match the repository.
    • README.md does not match the repository.

    Looked for the crate in common/. Fetched https://github.com/zdz/serverstatus-rust.git 03b626d6bfe42004ebd79b9dbce316028ca8719f.

    Checked on 2024-07-28

    This check is experimental.

    Forum thread

  • Dependency prost 0.12 is significantly outdated

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

    prost versions

  • Dependency tonic 0.11 is significantly outdated

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

    tonic versions

  • Dependency tonic-build 0.11 is significantly outdated

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

    tonic-build versions

  • Incorrect category

    Crate's categories property in Cargo.toml contains 'monitoring-tools', which isn't a category we recognize

    lib.rs has simplified and merged some of crates.io categories. Please file a bug if we got it wrong.

    List of available categories

  • The Cargo package has no git commit information

    Before publishing a package, make sure all packaged files are committed to the repository, and there are no "dirty" files. Push this commit to crate's public repository.

    To protect against supply chain attacks similar to CVE-2024-3094, lib.rs will soon start flagging non-reproducible packages without public source code as suspicious. Currently only git repositories are supported (but may be hosted anywhere, not just GitHub). If you'd like a different SCM supported, please file a feature request.

    More info

  • Dependency protobuf-src 1 is a bit outdated

    Consider upgrading to 2.1.0+27.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.

    protobuf-src versions

  • 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

  • Imprecise dependency requirement protobuf-src = 1

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

    protobuf-src versions

• stat_client

  • Dependency prost 0.12 is significantly outdated

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

    prost versions

  • Dependency tokio-rustls 0.25 is significantly outdated

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

    tokio-rustls versions

  • Dependency tonic 0.11 is significantly outdated

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

    tonic versions

  • Imprecise dependency requirement anyhow = 1

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

  • Incorrect category

    Crate's categories property in Cargo.toml contains 'monitoring-tools', which isn't a category we recognize

    List of available categories

  • The Cargo package has no git commit information

    Before publishing a package, make sure all packaged files are committed to the repository, and there are no "dirty" files. Push this commit to crate's public repository.

    More info

  • Dependency reqwest 0.11 is outdated

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

    reqwest versions

  • Dependency sysinfo 0.30.7 is outdated

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

    sysinfo versions

  • Dependency tower 0.4 is outdated

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

    tower versions

  • Failed to verify create's content against its repository

    Verified 17 out of 18 files (includes 2 Cargo-generated).

    • warning: The crates.io package has no commit hash associated with it.
      • Publish a new version, without using --allow-dirty flag. Make sure all changes are committed before publishing. Use include/exclude in Cargo.toml to omit unnecessary files.

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

    • Cargo.lock not found.
    • sys_info.rs does not match the repository.

    Looked for the crate in client/. Fetched https://github.com/zdz/serverstatus-rust.git tagged v1.8.1 (1dd5c4183713db5ca444f9cd85a83d58702937f3).

    Checked on 2024-07-24

    Forum thread

• stat_server

  • Dependency prost 0.12 is significantly outdated

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

    prost versions

  • Dependency tokio-rustls 0.25 is significantly outdated

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

    tokio-rustls versions

  • Dependency tonic 0.11 is significantly outdated

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

    tonic versions

  • Imprecise dependency requirement anyhow = 1

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

  • The Cargo package has no git commit information

    Before publishing a package, make sure all packaged files are committed to the repository, and there are no "dirty" files. Push this commit to crate's public repository.

    More info

  • Dependency axum 0.7.4 is outdated

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

    axum versions

  • Dependency axum-extra 0.9.2 is outdated

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

    axum-extra versions

  • Dependency minijinja 1.0 is outdated

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

    minijinja versions

  • Dependency reqwest 0.11 is outdated

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

    reqwest versions

  • Dependency tower-http 0.5 is outdated

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

    tower-http versions

  • Failed to verify create's content against its repository

    Verified 17 out of 23 files (includes 2 Cargo-generated).

    • warning: The crates.io package has no commit hash associated with it.
      • Publish a new version, without using --allow-dirty flag. Make sure all changes are committed before publishing. Use include/exclude in Cargo.toml to omit unnecessary files.

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

    • Cargo.lock not found.
    • src/
      • stats.rs does not match the repository.
      • auth.rs does not match the repository.
      • http.rs does not match the repository.
      • main.rs does not match the repository.
      • config.rs does not match the repository.
      • alert.rs not found.

    Looked for the crate in server/. Fetched https://github.com/zdz/serverstatus-rust.git tagged v1.8.1 (1dd5c4183713db5ca444f9cd85a83d58702937f3).

    Checked on 2024-07-28

    Forum thread

  • Incorrect category

    Crate's categories property in Cargo.toml contains 'monitoring-tools', which isn't a category we recognize

    List of available categories

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