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.

• askar-crypto

  • Dependency block-modes 0.9 has issues

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

    block-modes crate

  • Dependency animo-secure-env 0.4 is slightly outdated

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

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

    animo-secure-env versions

  • Imprecise dependency requirement curve25519-dalek = 4

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

    curve25519-dalek versions

  • Optional dependency 'uuid' 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 'uuid', 'hkdf', 'x25519-dalek', 'block-modes', 'crypto_box_rs', 'p384', 'curve25519-dalek', 'ed25519-dalek', 'hmac', 'p256', 'chacha20poly1305', 'elliptic-curve', 'secure-env', 'bls12_381', 'cbc', 'aes-core', 'cipher', 'aes-gcm', 'k256' may have been unintentional.

    Crate features

• aries-bbssignatures, aries-askar, indy-vdr

  • Cryptocurrency crate

    This crate has been classified as related to cyrptocurrencies. If you believe this categorization is a mistake, then please review crate's categories and keywords, or file a bug. If it is related, then please reconsider your choices, and yank it.

    Author of this site is firmly convinced that cryptocurrencies have a net-negative effect on society.

• async-resource

  • README missing from the repository

    We've searched https://github\.com/andrewwhitehead/async\-resource\-rs\.git and could not find a README file there.

  • Dependency concurrent-queue 1.1 is significantly outdated

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

    concurrent-queue 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 option-lock 0.1 is a bit outdated

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

    option-lock versions

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

    Use OR instead of /.

    SPDX license list

  • Missing categories

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

• askar-storage

  • Dependency itertools 0.13 is outdated

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

    itertools versions

• anoncreds-clsignatures, indy-data-types, indy-credx, indy-utils, indy-blssignatures, indy-wql, indy-test-utils, askar-bbs

  • Cryptocurrency crate

    This crate has been classified as related to cyrptocurrencies. If you believe this categorization is a mistake, then please review crate's categories and keywords, or file a bug. If it is related, then please reconsider your choices, and yank it.

• flex-alloc

  • Imprecise dependency requirement zeroize = 1

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

    zeroize versions

• option-lock

  • Dependency criterion 0.3 is outdated

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

    criterion versions

  • Latest stable release is old

    It's been over 3 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").

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

    Maintenance status field docs

• suspend

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

    Use OR instead of /.

    SPDX license list

• suspend, suspend-channel, maybe-cell

  • Latest stable release is old

    It's been over 4 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

• maybe-cell

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

    Use OR instead of /.

    SPDX license list

• async-resource, suspend-core

  • Latest stable release is old

    It's been over 4 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

• flex-alloc-secure

  • Dependency flex-alloc 0.0.4 is slightly outdated

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

    flex-alloc versions

  • Imprecise dependency requirement zeroize = 1

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

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