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.

• foundationdb

  • Dependency rand 0.8.5 is a bit outdated

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

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

    rand versions

  • Optional dependency 'serde_bytes' exposed as an implicit feature

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

    Crate features

• xdelta3

  • Latest stable release is old

    It's been over 5 years. How did the experiment go? Make a new release, either to refresh it, or to set

    [badges.maintenance]
    status = "deprecated"
    

    (or "as-is", "passively-maintained").

    If the crate is truly stable, why not make a 1.0.0 release?

    Maintenance status field docs

  • 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 bindgen 0.52 is significantly outdated

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

    bindgen versions

  • Dependency rand 0.6 is significantly outdated

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

    rand versions

  • Published crate contains binary files

    The crate contains binary files (obscure autoconf code). Crates are meant to be compiled from source. Please check that you haven't published temporary build files by accident. If you have test fixtures, consider excluding them from crates-io tarball, since Cargo doesn't run tests from crates-io packages.

    Audit page

• s2

  • Dependency bigdecimal 0.3.0 is outdated

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

    bigdecimal versions

  • Dependency rand 0.8.5 is a bit outdated

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

    rand versions

  • Failed to verify create's content against its repository

    Verified 39 out of 40 files (includes 3 Cargo-generated).

    • warning: Crate tarball has been published from the commit f32a21a45ff465df382e78770c625dc2f3199be6, which is not in the repository.
      • Create git tags after comitting any changes, and commit changes after bumping versions and running cargo update.
    • warning: Found a Cargo.toml for this package in its repo (via tags), but the version was different.
      • Make sure to commit and tag after bumping the version number.
    • 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.lock not found.
    • Cargo.toml.orig does not match the repository.

    Fetched https://github.com/yjh0502/rust-s2.git c00e91ea2ce69c2f5d8ba316cb7487765879f6ae.

    Checked on 2024-10-04

    This check is experimental.

    Forum thread

  • Missing categories

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

    List of available categories

  • Using outdated edition for no reason

    We estimate that this crate requires at least Rust 1.60, which is newer than the last 2018-edition compiler. You can upgrade without breaking any compatibility. Run cargo fix --edition and update edition="…" in Cargo.toml.

    Using the latest edition helps avoid old quirks of the compiler, and ensures Rust code has consistent syntax and behavior across all projects.

    The Edition Guide

• foundationdb, foundationdb-gen, foundationdb-sys, sse, serv

  • License MIT/Apache-2.0 is not in SPDX syntax

    Use OR instead of /.

    SPDX license list

• float_extras

  • Latest stable release is old

    It's been over 7 years. Is this crate still maintained? Make a new release, either to refresh it, or to set

    [badges.maintenance]
    status = "deprecated"
    

    (or "as-is", "passively-maintained").

    Maintenance status field docs

  • 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

• serv

  • Dependency bytes 0.4 is significantly outdated

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

    bytes versions

  • Dependency error-chain 0.12 has issues

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

    error-chain crate

  • Dependency fst 0.3 is significantly outdated

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

    fst versions

  • Dependency futures 0.1 has issues

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

    futures crate

  • Dependency http 0.1 is significantly outdated

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

    http versions

  • Dependency hyper 0.12.13 is significantly outdated

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

    hyper versions

  • Dependency serde_qs 0.4 is significantly outdated

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

    serde_qs versions

  • Dependency tokio 0.1 has issues

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

    tokio crate

  • Dependency tokio-current-thread 0.1 has issues

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

    tokio-current-thread crate

  • Dependency tokio-io 0.1 has issues

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

    tokio-io crate

  • Dependency tokio-uds 0.2 has issues

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

    tokio-uds crate

  • Dependency url 1 is significantly outdated

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

    url 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

  • Missing categories

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

    List of available categories

• sse

  • Dependency bytes 0.4 is significantly outdated

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

    bytes versions

  • Dependency error-chain 0.12 has issues

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

    error-chain crate

  • Dependency futures 0.1 has issues

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

    futures crate

  • Dependency http 0.1 is significantly outdated

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

    http versions

  • Dependency hyper 0.12 is significantly outdated

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

    hyper versions

  • Dependency tokio 0.1 has issues

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

    tokio crate

  • Dependency tokio-timer 0.2 has issues

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

    tokio-timer crate

  • Dependency bitflags 1 is outdated

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

    bitflags versions

  • Imprecise dependency requirement bitflags = 1

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

    bitflags versions

  • Missing categories

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

    List of available categories

• cql

  • 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

  • Missing categories

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

    List of available categories

• cql, sse, serv

  • Latest stable release is old

    It's been over 6 years. Is this crate still maintained? Make a new release, either to refresh it, or to set

    [badges.maintenance]
    status = "deprecated"
    

    (or "as-is", "passively-maintained").

    Maintenance status field docs

• foundationdb-sys

  • *-sys crate without links property

    If this crate uses C libraries with public symbols, consider adding links = "foundationdb" to crate's Cargo.toml to avoid other libraries colliding with them. Note that the links property adds exclusivity to dependency resolution, but doesn't do any linking.

    This is also needed to protect your crate from duplicate older versions of itself. C symbols are global, and duplicate symbols can cause all sorts of breakage.

  • Dependency bindgen 0.70.1 is outdated

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

    bindgen versions

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