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.

• devolutions-crypto

  • Dependency arbitrary 0.4.7 is significantly outdated

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

    arbitrary versions

  • Published crate doesn't match its repository

    Partially verified 194 files (includes 3 Cargo-generated).

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

    • Cargo.lock does not match the repository.

    Fetched https://github.com/devolutions/devolutions-crypto.git 1af1ba8395bcf8e5d20aa6031b97679531b9a6c7.

    Checked on 2025-02-02

    This check is experimental.

    Forum thread

  • Dependency getrandom 0.2 is outdated

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

    getrandom versions

  • Dependency rand 0.8 is a bit outdated

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

    rand versions

  • Dependency rand_core 0.6 is a bit outdated

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

    rand_core versions

  • Dependency strum 0.26 is outdated

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

    strum versions

  • Dependency typed-builder 0.20.0 is outdated

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

    typed-builder versions

  • Imprecise dependency requirement byteorder = 1

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

    byteorder versions

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["cryptography"] 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 = ["asymmetric", "generate-key", "cryptography", "password-hash", "signature"] (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 'serde-wasm-bindgen' 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-wasm-bindgen', 'wasm-bindgen', 'js-sys', 'arbitrary' may have been unintentional.

    Crate features

  • Published crate contains binary files

    The crate contains binary files (JAR file). 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

• slauth

  • Dependency sha-1 0.10 has issues

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

    sha-1 crate

  • Dependency x509-parser 0.15.0 is significantly outdated

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

    x509-parser versions

  • Dependency base32 0.4 is outdated

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

    base32 versions

  • 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 getrandom 0.2 is outdated

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

    getrandom versions

  • Dependency rand 0.8.5 is a bit outdated

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

    rand 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

  • Failed to verify create's content against its repository

    Partially verified 112 files (includes 3 Cargo-generated).

    • warning: Crate tarball has been published from a different commit than the commit tagged by git tag '0.7.14'.
      • Create git tags after comitting any changes, and commit changes after bumping versions and running cargo update.

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

    • Cargo.lock not found.

    Fetched https://github.com/devolutions/slauth.git 595bb1df5c3957119cde998719fb884b0c69baeb.

    Checked on 2025-04-12

    Forum thread

  • Missing categories

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

    List of available categories

  • Optional dependency 'byteorder' 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 'byteorder', 'serde_repr', 'bytes', 'ed25519-dalek', 'serde', 'serde_bytes', 'base64', 'untrusted', 'uuid', 'jni', 'ring', 'http', 'serde_derive', 'webpki', 'p256', 'serde_cbor', 'serde_json', 'indexmap' may have been unintentional.

    Crate features

  • Published crate contains binary files

    The crate contains binary files (ELF lib, JAR file). 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

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