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.

• mopro-ffi

  • 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

  • Dependency color-eyre =0.6.2 is significantly outdated

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

    color-eyre versions

  • Dependency thiserror =2.0.3 is significantly outdated

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

    thiserror versions

  • Dependency uniffi =0.28.0 is significantly outdated

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

    uniffi versions

  • Locked dependency version ark-bn254 =0.4.0

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    ark-bn254 versions

  • Locked dependency version color-eyre =0.6.2

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    color-eyre versions

  • Locked dependency version thiserror =2.0.3

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    thiserror versions

  • Locked dependency version uniffi =0.28.0

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    uniffi versions

  • Published crate doesn't match its repository

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

    • warning: Crate tarball has been published from a different commit than the commit tagged by git tag 'v0.1.1'.
      • 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.toml.orig does not match the repository.

    Looked for the crate in mopro-ffi/. Fetched https://github.com/zkmopro/mopro.git 441e646b657788fbcf78a1e76c8f459edfb3a58d.

    Checked on 2025-02-23

    This check is experimental.

    Forum thread

  • Dependency ark-bls12-381 0.4.0 is slightly outdated

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

    ark-bls12-381 versions

  • Dependency ark-bn254 =0.4.0 is slightly outdated

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

    ark-bn254 versions

  • Dependency ark-ff 0.4.0 is a bit outdated

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

    ark-ff versions

  • Dependency bincode 1.3.3 is slightly outdated

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

    bincode versions

  • Missing keywords

    Help users find your crates. Add keywords = ["proving", "mobile", "client-side", "zk", "mopro"] (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 'ark-bls12-381' 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 'ark-bls12-381', 'rust-witness', 'ark-ff', 'ark-bn254', 'circom-prover' may have been unintentional.

    Crate features

• circom-prover

  • Dependency ark-ec =0.4.1 is significantly outdated

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

    ark-ec versions

  • Dependency ark-ff =0.4.1 is significantly outdated

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

    ark-ff versions

  • Dependency ark-poly =0.4.1 is significantly outdated

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

    ark-poly versions

  • Dependency ark-serialize =0.4.1 is significantly outdated

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

    ark-serialize versions

  • Locked dependency version ark-bn254 =0.4.0

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    ark-bn254 versions

  • Locked dependency version ark-crypto-primitives =0.4.0

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    ark-crypto-primitives versions

  • Locked dependency version ark-ec =0.4.1

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    ark-ec versions

  • Locked dependency version ark-ff =0.4.1

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    ark-ff versions

  • Locked dependency version ark-groth16 =0.4.0

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    ark-groth16 versions

  • Locked dependency version ark-poly =0.4.1

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    ark-poly versions

  • Locked dependency version ark-serialize =0.4.1

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    ark-serialize versions

  • Locked dependency version ark-std =0.4.0

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    ark-std versions

  • Dependency ark-bls12-381 0.4.0 is slightly outdated

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

    ark-bls12-381 versions

  • Dependency ark-bn254 =0.4.0 is slightly outdated

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

    ark-bn254 versions

  • Dependency ark-crypto-primitives =0.4.0 is a bit outdated

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

    ark-crypto-primitives versions

  • Dependency ark-groth16 =0.4.0 is a bit outdated

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

    ark-groth16 versions

  • Dependency ark-relations 0.4 is outdated

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

    ark-relations versions

  • Dependency ark-std =0.4.0 is a bit outdated

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

    ark-std versions

  • Dependency hex-literal 0.4.1 is outdated

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

    hex-literal versions

  • Dependency rand 0.8 is a bit outdated

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

    rand versions

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["circom", "prover", "witness", "circuit", "verifying"] (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 'ark-ec' 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 'ark-ec', 'ark-bls12-381', 'rust-witness', 'witnesscalc-adapter', 'ark-bn254', 'ark-relations', 'ark-ff', 'ark-std', 'ark-crypto-primitives', 'ark-groth16', 'ark-poly', 'ark-serialize' may have been unintentional.

    Crate features

• rust-rapidsnark

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["proof", "rapidsnark", "witness", "verify", "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.

• witnesscalc-adapter

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["adapter", "circuit", "witnesscalc", "witness", "convert"] (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.

• rust-witness

  • 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 = ["circom", "witness", "circuit", "generator", "generate"] (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.

• ark-zkey

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["serialization", "zkey", "read", "faster", "friendly"] (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.

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