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.

• boringtun

  • Dependency jni 0.19.0 is significantly outdated

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

    jni versions

  • Dependency mock_instant 0.2 is significantly outdated

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

    mock_instant versions

  • Dependency nix 0.25 is significantly outdated

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

    nix versions

  • Dependency socket2 0.4.7 is significantly outdated

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

    socket2 versions

  • Dependency x25519-dalek =2.0.0-rc.3 is significantly outdated

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

    x25519-dalek versions

  • Imprecise dependency requirement thiserror = 1

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

    thiserror versions

  • Published crate doesn't match its repository

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

    Looked for the crate in boringtun/. Fetched https://github.com/cloudflare/boringtun.git 18eaf59c9c9718850c63e1c82ba933e09224d3dd.

    Checked on 2024-08-10

    This check is experimental.

    Forum thread

  • Dependency base64 0.13 is outdated

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

    base64 versions

  • Dependency rand_core 0.6.3 is a bit outdated

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

    rand_core versions

  • Dependency ring 0.16 is outdated

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

    ring versions

  • Dependency thiserror 1 is a bit outdated

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

    thiserror versions

  • Missing categories

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

  • Missing keywords

    Help users find your crates. Add keywords = ["wireguard", "speed", "sockets", "cloudflare"] (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.

  • Optional dependency 'socket2' 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 'socket2', 'tracing-subscriber', 'jni', 'mock_instant', 'thiserror' may have been unintentional.

    Crate features

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

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