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.

• addchain

  • Published crate doesn't match its repository

    Partially verified 14 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/str4d/addchain.git f8b6d01889bc546d12a08550011708c6265920aa.

    Checked on 2026-03-15

    This check is experimental.

    Forum thread

  • Missing keywords

    Help users find your crates. Add keywords = ["addition-chain", "generator", "step", "compute", "algorithm"] (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.

• group

  • Missing keywords

    Help users find your crates. Add keywords = ["elliptic-curve-group", "create", "utilities", "rfc-process", "follow"] (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 'rand_xorshift' 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 'rand_xorshift', 'rand', 'memuse' may have been unintentional.

    Crate features

• ff

  • Missing keywords

    Help users find your crates. Add keywords = ["finite-fields", "prime-field", "traits", "rfc-process", "derive"] (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 'bitvec' 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 'bitvec', 'byteorder', 'ff_derive' may have been unintentional.

    Crate features

• group, ff, pairing, bellman, memuse, fpe, jubjub, bls12_381, schemerz

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

    Use OR instead of /.

    SPDX license list

• group, pairing, x509, bls12_381, age-core, age-plugin, siso

  • 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

• ff, bellman, jubjub, halo2_poseidon

  • Imprecise dependency requirement bitvec = 1

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

    bitvec versions

• ff, bellman, jubjub

  • Missing categories

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

    List of available categories

• pairing

  • Latest prerelease is old

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

    Users pay attention to the latest release date. Even if the crate is perfectly fine as-is, users may not know that.

    Maintenance status field docs

  • Dependency group =0.14.0-pre.0 is significantly outdated

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

    group versions

  • Missing keywords

    Help users find your crates. Add keywords = ["pairing-friendly-elliptic-curve", "bls12-381", "rfc-process"] (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.

• c64

  • Dependency bare-metal 1 has issues

    It has been losing active users, which may be a sign it's deprecated or obsolete. Consider replacing it with a different crate.

    bare-metal crate

  • No repository property

    Specify git repository URL in Cargo.toml to help users find more information, contribute, and for lib.rs to read more info.

  • Dependency bitflags 1 is outdated

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

    bitflags versions

  • Imprecise dependency requirement bitflags = 1

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

    bitflags versions

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["commodore", "commodore-c64", "driver", "platform", "docker"] (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.

• x509

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

    Help users find your crates. Add keywords = ["serialization", "x509-certificate", "api", "rfc"] (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.

• flipperzero-test

  • Failed to verify create's content against its repository

    Verified 5 out of 6 files (includes 3 Cargo-generated).

    • warning: The crates.io package has no information about its path inside its repository.
    • error: Crate repo contained a malformed or forbidden path (suspicious path): 'crates/../README.md'
      • File a bug https://gitlab.com/lib.rs/main if you think it should work

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

    • Cargo.lock not found.
    • README.md exists, but elsewhere in the repo.

    Looked for the crate in crates/test/. Fetched https://github.com/flipperzero-rs/flipperzero-rs.git tagged v0.16.0 (08339c46b847610cc3a8a8a17651e7000e773ca9).

    Checked on 2025-12-28

    Forum thread

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["flipper-zero", "harness-for-flipper-zero", "sdk-version", "applications"] (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.

• schemerz-rusqlite

  • Published crate doesn't match its repository

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

    Looked for the crate in schemerz-rusqlite/. Fetched https://github.com/zcash/schemerz.git de4244d4f4e5f06232311619195996a7485459e7.

    Checked on 2025-10-31

    Forum thread

  • Dependency rusqlite 0.37 is significantly outdated

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

    rusqlite versions

  • Imprecise dependency requirement uuid = 1

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

    uuid versions

• bellman

  • Missing keywords

    Help users find your crates. Add keywords = ["zk-snarks", "build", "scalar-field", "math", "groth16"] (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 'lazy_static' 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 'lazy_static', 'log', 'num_cpus', 'rayon', 'pairing', 'crossbeam-channel' may have been unintentional.

    Crate features

• tev

  • Imprecise dependency requirement anyhow = 1

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

  • Published crate doesn't match its repository

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

    Fetched https://github.com/str4d/tev.git 4810bb6c6edf890b5f8a66d1d92fd11c56276aa6.

    Checked on 2025-01-12

    Forum thread

  • Dependency fuser 0.15 is outdated

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

    fuser versions

  • Dependency nom 7 is a bit outdated

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

    nom versions

  • Dependency sha1 0.10 is a bit outdated

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

    sha1 versions

  • Dependency widestring 0.4 is significantly outdated

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

    widestring versions

  • Dependency zip 2 is outdated

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

    zip versions

• memuse

  • Published crate doesn't match its repository

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

    Fetched https://github.com/str4d/memuse.git d7144494b888b2a1be266685bb36ed980056c5f6.

    Checked on 2024-12-15

    Forum thread

  • Dependency nonempty 0.7 is outdated

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

    nonempty versions

• age-core

  • Dependency base64 0.21 is significantly outdated

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

    base64 versions

  • Dependency hkdf 0.12 is a bit outdated

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

    hkdf versions

  • Dependency nom 7 is a bit outdated

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

    nom versions

  • Dependency rand 0.8 is outdated

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

    rand versions

  • Dependency sha2 0.10 is a bit outdated

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

    sha2 versions

  • Latest stable release is old

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

    Maintenance status field docs

  • Missing keywords

    Help users find your crates. Add keywords = ["age-encryption", "across", "recipient", "beta", "file-encryption"] (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 'tempfile' exposed as an implicit feature

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

    Crate features

• zcash_proofs, zcash_primitives, zcash_keys, zcash_client_backend, pasta_curves, reddsa, orchard, zcash_address, zcash_note_encryption, zip32

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

• bellman, fpe, jubjub, bls12_381

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

    Maintenance status field docs

• bellman, jubjub, bls12_381, vrf-r255

  • Dependency rand_core 0.6 is outdated

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

    rand_core versions

• bellman, jubjub, bls12_381, halo2_poseidon

  • Dependency ff 0.13 is slightly outdated

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

    ff versions

• bellman, jubjub, bls12_381, halo2_poseidon

  • Dependency group 0.13 is slightly outdated

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

    group versions

• i2p_snow

  • Dependency failure ^0.1 has issues

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

    failure crate

  • Dependency failure_derive ^0.1 has issues

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

    failure_derive crate

  • Dependency rand ^0.6 is significantly outdated

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

    rand versions

  • Dependency rand_core ^0.4 is significantly outdated

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

    rand_core versions

  • Dependency ring ^0.14.0 is significantly outdated

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

    ring versions

  • Dependency rust-crypto ^0.2 has issues

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

    rust-crypto crate

  • Dependency rustc_version ^0.2 is significantly outdated

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

    rustc_version versions

  • Dependency smallvec ^0.6.3 is significantly outdated

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

    smallvec versions

  • Dependency x25519-dalek ^0.4 is significantly outdated

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

    x25519-dalek versions

  • 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

  • Dependency hacl-star 0.0.13 is outdated

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

    hacl-star versions

• yubikey, flipperzero-test, shardtree, i2p_snow

  • docs.rs build failed

    docs.rs site failed to build the crate, so users will have trouble finding the documentation. Docs.rs supports multiple platforms and custom configurations, so you can make the build work even if normal crate usage has special requirements.

    Docs.rs doesn't need to run or even link any code, so system dependencies can simply be skipped. You can also set cfg() flags just for docs.rs and use them to hide problematic code.

    Detecting docs.rs

• bls12_381

  • Dependency digest 0.9 is significantly outdated

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

    digest versions

  • Missing keywords

    Help users find your crates. Add keywords = ["experimental", "target", "bit", "nightly", "math"] (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.

• schemerz

  • Dependency indexmap 1 is significantly outdated

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

    indexmap versions

  • Published crate doesn't match its repository

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

    Looked for the crate in schemerz/. Fetched https://github.com/zcash/schemerz.git 23a5f277a0b7a0b2209d801aaf983a35d64a3d6d.

    Checked on 2024-10-19

    Forum thread

  • Dependency daggy 0.8 is outdated

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

    daggy versions

  • Dependency thiserror 1.0 is outdated

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

    thiserror versions

  • Imprecise dependency requirement indexmap = 1

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

    indexmap versions

• yubikey

  • Dependency base16ct 0.2 is slightly outdated

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

    base16ct versions

  • Imprecise dependency requirement subtle = 2

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

    subtle versions

• backflip

  • No repository property

    Specify git repository URL in Cargo.toml to help users find more information, contribute, and for lib.rs to read more info.

  • Dependency nom 7.1 is a bit outdated

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

    nom versions

  • Failed to verify create's content against its repository

    Verified 11 out of 12 files (includes 3 Cargo-generated).

    • warning: Crate tarball has been published from the commit 1b5b454ac65af9a8c00ae62a66291ac12a81c512, 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 does not match the repository.
    • Cargo.toml.orig does not match the repository.

    Fetched https://github.com/str4d/backflip.git 19d81e33dee3482cff2b0c119190c1b6e2ce74dd.

    Checked on 2026-05-24

    Forum thread

  • Missing keywords

    Help users find your crates. Add keywords = ["flipper-zero", "trick", "perform", "ir", "button"] (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.

• bridgetree

  • Imprecise dependency requirement proptest = 1

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

    proptest versions

  • Missing keywords

    Help users find your crates. Add keywords = ["merkle-tree", "checkpointing", "state-tree", "witnesses", "bridge"] (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 'proptest' exposed as an implicit feature

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

    Crate features

• siso

  • No repository property

    Specify git repository URL in Cargo.toml to help users find more information, contribute, and for lib.rs to read more info.

  • Missing keywords

    Help users find your crates. Add keywords = ["emulation", "ibm", "io", "team", "work-in-progress"] (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 'gumdrop' 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 'gumdrop', 'tracing-subscriber' may have been unintentional.

    Crate features

• fpe

  • Dependency cbc 0.1 is slightly outdated

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

    cbc versions

  • Dependency cipher 0.4 is a bit outdated

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

    cipher versions

• bcrypt-pbkdf, pinentry

  • Imprecise dependency requirement zeroize = 1

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

    zeroize versions

• age-plugin

  • Dependency base64 0.21 is significantly outdated

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

    base64 versions

  • Dependency bech32 0.9 is outdated

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

    bech32 versions

  • Missing keywords

    Help users find your crates. Add keywords = ["encryption", "age-encryption", "recipient", "identity", "file-encryption"] (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.

• atproto-devtool

  • Dependency getrandom 0.2 is outdated

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

    getrandom versions

  • Dependency hickory-resolver 0.25 is outdated

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

    hickory-resolver versions

• backflip, zk, groth16

  • Missing categories

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

    List of available categories

• flipperzero-test-macros

  • Failed to verify create's content against its repository

    Verified 6 out of 7 files (includes 3 Cargo-generated).

    • warning: The crates.io package has no information about its path inside its repository.
    • error: Crate repo contained a malformed or forbidden path (suspicious path): 'crates/../README.md'
      • File a bug https://gitlab.com/lib.rs/main if you think it should work

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

    • Cargo.lock not found.
    • README.md exists, but elsewhere in the repo.

    Looked for the crate in crates/test/macros/. Fetched https://github.com/flipperzero-rs/flipperzero-rs.git tagged v0.16.0 (08339c46b847610cc3a8a8a17651e7000e773ca9).

    Checked on 2025-12-28

    Forum thread

  • Dependency syn 1 is significantly outdated

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

    syn versions

  • Imprecise dependency requirement syn = 1

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

    syn versions

• schemerz-postgres

  • Published crate doesn't match its repository

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

    Looked for the crate in schemerz-postgres/. Fetched https://github.com/zcash/schemerz.git f4f8d0c37170b1527441db4ca2cdea28e60f95c7.

    Checked on 2024-10-19

    Forum thread

  • Imprecise dependency requirement uuid = 1

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

    uuid versions

• zcash_transparent, zcash_client_sqlite, halo2_proofs, zcash_spec, equihash, incrementalmerkletree, pczt, zcash_encoding, sapling-crypto, f4jumble, halo2_gadgets, sinsemilla, libzcash_script, zcash_history, halo2, zcash_extensions, zcash, zallet

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

• shardtree

  • Imprecise dependency requirement proptest = 1

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

    proptest versions

  • Missing keywords

    Help users find your crates. Add keywords = ["merkle-tree", "checkpointing", "insertion", "witnesses", "marked"] (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.

• jubjub

  • Missing keywords

    Help users find your crates. Add keywords = ["elliptic-curve-group", "constant", "constant-time", "audit", "standard"] (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.

• halo2_poseidon

  • Failed to verify create's content against its repository

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

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

    Looked for the crate in halo2_poseidon/. Fetched https://github.com/zcash/halo2.git f066ace1f234d7fe1908851ed86b1801e0b1ffea.

    Checked on 2025-07-20

    Forum thread

  • Missing keywords

    Help users find your crates. Add keywords = ["halo2", "halo", "poseidon", "hash", "algebraic"] (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.

• i2p_elgamal

  • Dependency num-bigint 0.2 is significantly outdated

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

    num-bigint versions

  • Dependency rand 0.5 is significantly outdated

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

    rand versions

  • Dependency sha2 0.7 is significantly outdated

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

    sha2 versions

  • 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

• vrf-r255

  • Dependency sha2 0.10 is a bit outdated

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

    sha2 versions

• groth16

  • Dependency ff 0.13 is slightly outdated

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

    ff versions

  • Dependency group 0.13 is slightly outdated

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

    group versions

  • Dependency rand_core 0.6 is outdated

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

    rand_core versions

  • Failed to verify create's content against its repository

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

    • warning: The crates.io package has no information about its path inside its repository.
    • warning: There is no matching git tag containing version '0.1.0'.
      • git tag v0.1.0 c4672fc2aa5e1e30f5b144df89faf2485278cb8d; git push origin --tags

    Looked for the crate in groth16/. Fetched https://github.com/zkcrypto/bellman.git c4672fc2aa5e1e30f5b144df89faf2485278cb8d.

    Checked on 2025-03-23

    Forum thread

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

    byteorder versions

  • Missing keywords

    Help users find your crates. Add keywords = ["bellman", "prover-verifier", "system"] (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.

• hazmat, hazmat-macros

  • 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

• zk

  • Dependency rand_core 0.6 is outdated

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

    rand_core versions

  • Missing keywords

    Help users find your crates. Add keywords = ["zero-knowledge-proofs", "traits-for-with-zero-knowledge"] (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.

• schemerz-postgres, i2p_elgamal, ff_derive

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

    Use OR instead of /.

    SPDX license list

• ire

  • Dependency bytes ^0.4 is significantly outdated

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

    bytes versions

  • Dependency clap ^2.26 is significantly outdated

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

    clap versions

  • Dependency cookie-factory ^0.2 is significantly outdated

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

    cookie-factory versions

  • Dependency ed25519-dalek ^0.4 is significantly outdated

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

    ed25519-dalek versions

  • Dependency env_logger ^0.4 is significantly outdated

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

    env_logger versions

  • Dependency flate2 ^0.2 is significantly outdated

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

    flate2 versions

  • Dependency futures ^0.1 has issues

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

    futures crate

  • Dependency itertools ^0.6 is significantly outdated

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

    itertools versions

  • Dependency log ^0.3 is significantly outdated

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

    log versions

  • Dependency nom ^3.2 is significantly outdated

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

    nom versions

  • Dependency num ^0.1 is significantly outdated

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

    num versions

  • Dependency rand ^0.3 is significantly outdated

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

    rand versions

  • Dependency sha2 ^0.6 is significantly outdated

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

    sha2 versions

  • Dependency tokio-core ^0.1 has issues

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

    tokio-core crate

  • Dependency tokio-io ^0.1 has issues

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

    tokio-io crate

  • Latest stable release is old

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

• i2p_elgamal, ire, i2p

  • 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

• hazmat-macros

  • Could not fetch repository

    We've had trouble cloning git repo from https://github\.com/str4d/hazmat\.git

    At the moment we only support git, and attempt fetching when we index a new release. Cloning is necessary for lib.rs to gather data that is missing on crates.io, e.g. to correctly resolve relative URLs in README files, which depend on repository layout and non-standard URL schemes of repository hosts.

  • Dependency syn 1.0 is significantly outdated

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

    syn versions

• ff_derive

  • Imprecise dependency requirement syn = 2

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

    syn versions

  • No readme property

    Specify path to a README file for the project, so that information about is included in the crates.io tarball.

• i2p

  • Dependency log 0.3.7 is significantly outdated

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

    log versions

  • Dependency nom ^2.2 is significantly outdated

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

    nom versions

  • Dependency rand 0.3.15 is significantly outdated

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

    rand versions

  • Latest stable release is old

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

• hazmat-macros, plc, age-plugin-remote, halo2_dev, age-plugin-solo

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

• age-plugin-cac, plc, age-plugin-remote, halo2_dev, age-plugin-solo

  • Crate contains junk files

    The crate contains boilerplate Rust files with no real functionality.

• age

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/age ) failed. Please try again later.

• rage

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/rage ) failed. Please try again later.

• age-plugin-yubikey

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/age-plugin-yubikey ) failed. Please try again later.

No issues found in: bls yubikey-piv

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