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.

• serai-coordinator-tributary

  • Published crate doesn't match its repository

    Verified 7 out of 8 files (includes 2 Cargo-generated).

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

    • Cargo.toml.orig does not match the repository.

    Looked for the crate in coordinator/tributary/. Fetched https://github.com/serai-dex/serai.git 3c664ff05fb1d071b6f882e99fb0d050f44ea963.

    Checked on 2025-01-19

    This check is experimental.

    Forum thread

  • 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

  • Missing keywords

    Help users find your crates. Add keywords = ["serai", "coordinator", "tributary", "transaction", "definition"] (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.

• multiexp, serai-coordinator-tributary, generalized-schnorr, minimal-ed448, serai-full-stack-tests, nostd-io, bulletproofs-plus, curve-trees, msrv-shims, serai-orchestrator, serai-processor-bin

  • 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

• simple-request

  • Imprecise dependency requirement base64ct = 1

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

    base64ct versions

  • Missing categories

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

    List of available categories

  • Optional dependency 'base64ct' 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 'base64ct', 'zeroize', 'hyper-rustls' may have been unintentional.

    Crate features

• multiexp

  • Optional dependency 'rand_core' 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 'rand_core' may have been unintentional.

    Crate features

• multiexp, modular-frost, ciphersuite, dalek-ff-group, dkg, generalized-schnorr, dleq, schnorr-signatures, minimal-ed448, ff-group-tests, helioselene, ec-divisors, frost-schnorrkel, bulletproofs-plus, curve-trees

  • Dependency rand_core 0.6 is a bit outdated

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

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

    rand_core versions

• flexible-transcript

  • Optional dependency 'blake2' 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 'blake2' may have been unintentional.

    Crate features

• flexible-transcript, modular-frost, ciphersuite, dalek-ff-group, dleq, schnorr-signatures, helioselene, ec-divisors

  • Missing categories

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

    List of available categories

• alloy-simple-request-transport

  • Published crate doesn't match its repository

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

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

    • Cargo.toml.orig does not match the repository.

    Looked for the crate in networks/ethereum/alloy-simple-request-transport/. Fetched https://github.com/serai-dex/serai.git 834c16930b4fbb18edba291e6365881a61c101cb.

    Checked on 2024-12-15

    Forum thread

  • Dependency alloy-json-rpc 0.3 is significantly outdated

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

    alloy-json-rpc versions

  • Dependency alloy-transport 0.3 is significantly outdated

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

    alloy-transport versions

  • Imprecise dependency requirement serde_json = 1

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

  • Dependency tower 0.4 is outdated

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

    tower versions

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["alloy", "transport", "request", "simple-request", "client"] (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.

• serai-task

  • Failed to verify create's content against its repository

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

    • warning: The crates.io package has no information about its path inside its repository.
    • warning: Could not find Cargo.toml for this package in its repo (via tags).
      • Make sure the repository URL in Cargo.toml is correct
    • warning: Could not discover crate's location in its repository (via tags).
    • error: Manifest properties don't match: Existence of [lib] inconsistent: published=true; orig=false.

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

    • LICENSE does not match the repository.
    • README.md does not match the repository.
    • Cargo.toml.orig does not match the repository.
    • lib.rs not found.

    Fetched https://github.com/serai-dex/serai.git 066aa9eda4236fe26587e0980c5cff6455c2336e.

    Checked on 2024-12-29

    Forum thread

  • Imprecise dependency requirement tokio = 1

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

    tokio versions

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["task", "schema", "run", "serai", "services"] (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.

• generalized-schnorr

  • Failed to verify create's content against its repository

    Verified 2 out of 9 files (includes 2 Cargo-generated).

    • warning: The crates.io package has no information about its path inside its repository.
    • warning: Could not find Cargo.toml for this package in its repo (via tags).
      • Make sure the repository URL in Cargo.toml is correct
    • warning: Could not discover crate's location in its repository (via tags).
    • warning: Had to perform fuzzy search of the head branch due to lack of commit information in the package.
    • error: Manifest properties don't match: Existence of [lib] inconsistent: published=true; orig=false.

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

    • LICENSE does not match the repository.
    • README.md does not match the repository.
    • Cargo.toml.orig does not match the repository.
    • src/
      • mpc.rs not found.
      • lib.rs not found.
    • src/tests/
      • mpc.rs not found.
      • mod.rs not found.

    Fetched https://github.com/serai-dex/serai.git 91f8ec53d9119f837471583606d42b484e921567.

    Checked on 2024-12-08

    Forum thread

  • Optional dependency 'frost' 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 'frost' may have been unintentional.

    Crate features

• dleq

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

    thiserror versions

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

    Detecting docs.rs

  • Missing keywords

    Help users find your crates. Add keywords = ["discrete", "proof", "log", "curve", "equality"] (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 'thiserror' 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 'thiserror', 'multiexp' may have been unintentional.

    Crate features

• modular-frost

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

    thiserror versions

  • Dependency rand_chacha 0.3 is outdated

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

    rand_chacha versions

  • Optional dependency 'hex' 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 'hex', 'dalek-ff-group', 'minimal-ed448' may have been unintentional.

    Crate features

• serai-full-stack-tests

  • Failed to verify create's content against its repository

    Verified 2 out of 8 files (includes 1 Cargo-generated).

    • warning: The crates.io package has no commit hash associated with it.
      • Publish a new version, without using --allow-dirty flag. Make sure all changes are committed before publishing. Use include/exclude in Cargo.toml to omit unnecessary files.
    • warning: There is no matching git tag containing version '0.1.0'.
    • 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.toml.orig does not match the repository.
    • lib.rs does not match the repository.
    • mod.rs does not match the repository.
    • tests/full-stack/src/tests/
      • sign.rs exists, but elsewhere in the repo.
      • batch.rs exists, but elsewhere in the repo.
      • mod.rs exists, but elsewhere in the repo.
      • key_gen.rs exists, but elsewhere in the repo.

    Looked for the crate in tests/full-stack/. Fetched https://github.com/serai-dex/serai.git 2591b5ade968ed216a376474a7158eefe9c863f9.

    Checked on 2024-08-04

    Forum thread

  • Missing keywords

    Help users find your crates. Add keywords = ["full-stack", "serai", "full"] (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.

• dkg

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

    serde versions

  • Optional dependency 'thiserror' 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 'thiserror' may have been unintentional.

    Crate features

• helioselene

  • Failed to verify create's content against its repository

    Verified 3 out of 8 files (includes 1 Cargo-generated).

    • warning: The crates.io package has no commit hash associated with it.
      • Publish a new version, without using --allow-dirty flag. Make sure all changes are committed before publishing. Use include/exclude in Cargo.toml to omit unnecessary files.
    • 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'.
    • 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.toml.orig does not match the repository.
    • crypto/helioselene/src/
      • point.rs exists, but elsewhere in the repo.
      • field.rs exists, but elsewhere in the repo.
      • backend.rs exists, but elsewhere in the repo.
    • src/
      • backend.rs does not match the repository.
      • lib.rs does not match the repository.
      • point.rs does not match the repository.
      • field.rs does not match the repository.

    Looked for the crate in crypto/helioselene/. Fetched https://github.com/kayabanerve/fcmp-plus-plus.git 529a3fe9c54b7f701d7978b3dc781ea27ba7d7e5.

    Checked on 2024-08-04

    Forum thread

• monero, serai-db, serai-cosign, serai, build-solidity-contracts, serai-coordinator-substrate, serai-ethereum-relayer, tributary-sdk, ethereum-schnorr-contract, serai-processor-view-keys, serai-processor, mini-serai, serai-signals-primitives, serai-abi, deanonro, serai-env, serai-docker-tests, serai-processor-messages, serai-no-std-tests, monero-generators, monero-ffi, monero-bin-rpc, monero-payment-proofs, monero-base58, serai-processor-ethereum-deployer, serai-processor-ethereum-router, serai-processor-ethereum-contracts, serai-processor-smart-contract-scheduler, serai-processor-ethereum-erc20, serai-processor-ethereum-primitives

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

• bulletproofs-plus

  • Failed to verify create's content against its repository

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

    • warning: The crates.io package has no information about its path inside its repository.
    • warning: Could not find Cargo.toml for this package in its repo (via tags).
      • Make sure the repository URL in Cargo.toml is correct
    • warning: Could not discover crate's location in its repository (via tags).
    • warning: Had to perform fuzzy search of the head branch due to lack of commit information in the package.
    • error: Manifest properties don't match: Existence of [lib] inconsistent: published=true; orig=false.

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

    • LICENSE does not match the repository.
    • README.md does not match the repository.
    • Cargo.toml.orig does not match the repository.
    • lib.rs not found.

    Fetched https://github.com/kayabanerve/serai.git 09d96822ca17538aea756391fb7bd1677d6533f1.

    Checked on 2024-07-24

    Forum thread

  • Dependency ecip 0.1 has issues

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

    ecip crate

  • Dependency ciphersuite 0.3 is outdated

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

    ciphersuite versions

  • Dependency multiexp 0.3 is outdated

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

    multiexp versions

  • Optional dependency 'pasta_curves' 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 'pasta_curves' may have been unintentional.

    Crate features

• curve-trees

  • Failed to verify create's content against its repository

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

    • warning: The crates.io package has no information about its path inside its repository.
    • warning: Could not find Cargo.toml for this package in its repo (via tags).
      • Make sure the repository URL in Cargo.toml is correct
    • warning: Could not discover crate's location in its repository (via tags).
    • warning: Had to perform fuzzy search of the head branch due to lack of commit information in the package.
    • error: Manifest properties don't match: Existence of [lib] inconsistent: published=true; orig=false.

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

    • LICENSE does not match the repository.
    • README.md does not match the repository.
    • Cargo.toml.orig does not match the repository.
    • lib.rs exists, but elsewhere in the repo.

    Fetched https://github.com/kayabanerve/serai.git 09d96822ca17538aea756391fb7bd1677d6533f1.

    Checked on 2024-07-28

    Forum thread

  • Dependency ecip 0.1 has issues

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

    ecip crate

  • Dependency ciphersuite 0.3 is outdated

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

    ciphersuite versions

  • Dependency multiexp 0.3 is outdated

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

    multiexp versions

• modular-frost, dkg, dleq

  • Dependency thiserror 1 is a bit outdated

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

    Easy way to bump dependencies: cargo install cargo-edit; cargo upgrade -i; Also check out Dependabot service on GitHub.

    thiserror versions

• ciphersuite

  • Optional dependency 'std-shims' 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 'std-shims', 'sha2', 'sha3', 'elliptic-curve', 'k256', 'dalek-ff-group', 'minimal-ed448' may have been unintentional.

    Crate features

• dalek-ff-group, minimal-ed448, helioselene, bulletproofs-plus

  • Dependency crypto-bigint 0.5 is a bit outdated

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

    crypto-bigint versions

• serai-full-stack-tests, helioselene, msrv-shims, serai-orchestrator, serai-processor-bin

  • 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

• serai-full-stack-tests, zalloc, serai-processor-bin, embedwards25519, generalized-bulletproofs-ec-gadgets, secq256k1, serai-genesis-liquidity-primitives, serai-genesis-liquidity-pallet, musig, pedpop, wasm-cycles, ec-divisors-ct-tests, evrf-pvss, evrf-dkg, helioselene-ct-tests, evrf, polyseed, cryptonote, generalized-bulletproofs-circuit-abstraction

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

• serai-full-stack-tests, zalloc, embedwards25519, serai-processor-scanner, serai-processor-utxo-scheduler, serai-processor-transaction-chaining-scheduler, serai-processor-utxo-scheduler-primitives, serai-processor-frost-attempt-manager, serai-processor-primitives, serai-processor-signers, serai-processor-key-gen

  • Could not fetch repository

    We've had trouble cloning git repo from https://github\.com/serai\-dex/serai\.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.

• dkg, ff-group-tests, frost-schnorrkel

  • Missing categories

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

    List of available categories

• std-shims

  • Dependency hashbrown 0.14 is significantly outdated

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

    hashbrown versions

  • Missing categories

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

    List of available categories

• patchable-async-sleep

  • Imprecise dependency requirement tokio = 1

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

    tokio versions

  • Missing categories

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

    List of available categories

• minimal-ed448

  • Dependency generic-array 0.14 is slightly outdated

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

    generic-array versions

• frost-schnorrkel

  • Dependency schnorrkel 0.10 is significantly outdated

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

    schnorrkel versions

• zalloc

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["allocator", "memory", "zeroizing", "dealloc", "global-allocator"] (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.

• msrv-shims

  • 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 = ["msrv", "recent", "version", "re-exports", "objects"] (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.

• serai-orchestrator

  • Failed to verify create's content against its repository

    Verified 3 out of 26 files (includes 2 Cargo-generated).

    • warning: The crates.io package has no commit hash associated with it.
      • Publish a new version, without using --allow-dirty flag. Make sure all changes are committed before publishing. Use include/exclude in Cargo.toml to omit unnecessary files.
    • warning: There is no matching git tag containing version '0.0.1'.
    • 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.toml.orig does not match the repository.
    • Cargo.lock not found.
    • entry-dev.sh not found.
    • entry-dev.sh not found.
    • entry-dev.sh not found.
    • entry-dev.sh exists, but elsewhere in the repo.
    • hashes-v0.18.3.1.txt exists, but elsewhere in the repo.
    • .folder exists, but elsewhere in the repo.
    • .folder exists, but elsewhere in the repo.
    • .folder exists, but elsewhere in the repo.
    • .folder exists, but elsewhere in the repo.
    • .folder exists, but elsewhere in the repo.
    • mod.rs exists, but elsewhere in the repo.
    • Dockerfile does not match the repository.
    • entry-dev.sh not found.
    • src/
      • coordinator.rs does not match the repository.
      • main.rs does not match the repository.
      • message_queue.rs does not match the repository.
      • serai.rs does not match the repository.
      • processor.rs does not match the repository.
      • mimalloc.rs does not match the repository.
    • src/coins/
      • ethereum.rs not found.
      • monero.rs not found.
      • bitcoin.rs not found.

    Looked for the crate in orchestration/. Fetched https://github.com/serai-dex/serai.git 2591b5ade968ed216a376474a7158eefe9c863f9.

    Checked on 2024-08-04

    Forum thread

  • Missing keywords

    Help users find your crates. Add keywords = ["serai", "dockerfile", "generate", "orchestration"] (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.

• serai-processor-bin

  • 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 = ["processor", "serai", "binaries", "framework"] (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.

• embedwards25519, serai-processor-scanner, generalized-bulletproofs-ec-gadgets, secq256k1, serai-genesis-liquidity-primitives, serai-genesis-liquidity-pallet, serai-processor-utxo-scheduler, serai-processor-transaction-chaining-scheduler, serai-processor-utxo-scheduler-primitives, musig, pedpop, wasm-cycles, ec-divisors-ct-tests, serai-processor-frost-attempt-manager, evrf-pvss, serai-processor-primitives, serai-processor-signers, evrf-dkg, helioselene-ct-tests, evrf, polyseed, cryptonote, generalized-bulletproofs-circuit-abstraction, serai-processor-key-gen

  • Crate contains junk files

    The crate contains boilerplate Rust files with no real functionality.

• serai-processor-scanner, serai-processor-utxo-scheduler, serai-processor-transaction-chaining-scheduler, serai-processor-utxo-scheduler-primitives, serai-processor-frost-attempt-manager, serai-processor-primitives, serai-processor-signers, serai-processor-key-gen

  • No readme property

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

• serai-processor-signer

  • No readme property

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

• serai-processor-signer, serai-reproducible-runtime-tests, sui-serai, hedera-serai

  • Could not fetch repository

    We've had trouble cloning git repo from https://github\.com/serai\-dex/serai\.git

• serai-processor-signer, serai-reproducible-runtime-tests, serai-polyfill, sui-serai, hedera-serai, serai-dex-primitives, serai-coins-pallet, serai-signals-pallet, serai-message-queue, ecip

  • Crate contains junk files

    The crate contains boilerplate Rust files with no real functionality.

• serai-reproducible-runtime-tests, serai-polyfill, sui-serai, hedera-serai, serai-dex-primitives, serai-coins-pallet, serai-signals-pallet

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

• monero-fcmp-plus-plus, monero-oxide, solidity-fn-collision, serai-ethereum-processor, serai-bitcoin-processor, serai-monero-processor, serai-processor-ethereum-test-primitives, monero-serai-verify-chain, monero-address, monero-seed, monero-wallet, monero-borromean, monero-polyseed, monero-clsag, monero-mlsag, monero-primitives, monero-bulletproofs, monero-io, fcmp-plus-plus, full-chain-membership-proofs, monero-wallet-util, monero-wallet-util-no-std-tests, serai-primitives, serai-coordinator, serai-validator-sets-primitives, serai-client, ethereum-serai, serai-polyfills, filecoin-serai, near-serai, stellar-serai, aptos-serai, algorand-serai, solana-serai, cardano-serai, haven-serai, firo-serai, cosmos-serai, polkadot-serai, litecoin-serai, bitcoin-cash-serai, serai-staking-primitives, serai-staking-pallet, serai-reproducible-runtime, serai-in-instructions-primitives, serai-tokens-primitives, serai-dex-pallet, tributary-chain, serai-coins-primitives, serai-in-instructions-pallet, serai-runtime, serai-tokens-pallet, serai-coordinator-tests, serai-processor-tests, serai-node, serai-message-queue-tests, serai-validator-sets-pallet

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

• monero-bulletproofs-plus

  • Internal error

    We couldn't check this crate at this time, because: Crate needed for the dashboard Origin( lib.rs/crates/monero-bulletproofs-plus ). Please try again later.

• monero-wallet-scan

  • Internal error

    We couldn't check this crate at this time, because: Crate needed for the dashboard Origin( lib.rs/crates/monero-wallet-scan ). Please try again later.

• monero-full-chain-membership-proofs

  • Internal error

    We couldn't check this crate at this time, because: Crate needed for the dashboard Origin( lib.rs/crates/monero-full-chain-membership-proofs ). Please try again later.

• monero-wallet-send

  • Internal error

    We couldn't check this crate at this time, because: Crate needed for the dashboard Origin( lib.rs/crates/monero-wallet-send ). Please try again later.

• monero-serai-rpc

  • Internal error

    We couldn't check this crate at this time, because: Crate needed for the dashboard Origin( lib.rs/crates/monero-serai-rpc ). Please try again later.

• monero-decoys

  • Internal error

    We couldn't check this crate at this time, because: Crate needed for the dashboard Origin( lib.rs/crates/monero-decoys ). Please try again later.

• monero-ringct

  • Internal error

    We couldn't check this crate at this time, because: Crate needed for the dashboard Origin( lib.rs/crates/monero-ringct ). Please try again later.

• monero-wallet-core

  • Internal error

    We couldn't check this crate at this time, because: Crate needed for the dashboard Origin( lib.rs/crates/monero-wallet-core ). Please try again later.

• monero-core

  • Internal error

    We couldn't check this crate at this time, because: Crate needed for the dashboard Origin( lib.rs/crates/monero-core ). Please try again later.

• monero-zmq-rpc

  • Internal error

    We couldn't check this crate at this time, because: Crate needed for the dashboard Origin( lib.rs/crates/monero-zmq-rpc ). Please try again later.

• monero-generalized-schnorr-protocol

  • Internal error

    We couldn't check this crate at this time, because: Crate needed for the dashboard Origin( lib.rs/crates/monero-generalized-schnorr-protocol ). Please try again later.

• monero-fcmp-plus-plus-spend-auth

  • Internal error

    We couldn't check this crate at this time, because: Crate needed for the dashboard Origin( lib.rs/crates/monero-fcmp-plus-plus-spend-auth ). Please try again later.

• monero-arti-rpc

  • Internal error

    We couldn't check this crate at this time, because: Crate needed for the dashboard Origin( lib.rs/crates/monero-arti-rpc ). Please try again later.

• monero-full-chain-membership-proofs-plus-plus-spend-auth

  • Internal error

    We couldn't check this crate at this time, because: Crate needed for the dashboard Origin( lib.rs/crates/monero-full-chain-membership-proofs-plus-plus-spend-auth ). Please try again later.

• monero-full-chain-membership-proofs-plus-plus

  • Internal error

    We couldn't check this crate at this time, because: Crate needed for the dashboard Origin( lib.rs/crates/monero-full-chain-membership-proofs-plus-plus ). Please try again later.

• monero-arti-transport

  • Internal error

    We couldn't check this crate at this time, because: Crate needed for the dashboard Origin( lib.rs/crates/monero-arti-transport ). Please try again later.

No issues found in: generalized-bulletproofs bitcoin-serai monero-serai tendermint-machine dleq-serai transcript-trait

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