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.

• ark-ff

  • Dependency itertools 0.13 is 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.

    itertools versions

• ark-ff, ark-ec, ark-serialize, ark-poly, ark-std, ark-groth16

  • Imprecise dependency requirement rayon = 1

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

    rayon versions

• ark-crypto-primitives

  • Could not fetch repository

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

  • Optional dependency 'rayon' 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 'rayon', 'ark-r1cs-std', 'hashbrown', 'tracing', 'merlin' may have been unintentional.

    Crate features

• ark-bls12-381, ark-bls12-377, ark-bn254, ark-snark, ark-bw6-761, ark-ed-on-bn254, ark-relations, ark-crypto-primitives, ark-pallas, ark-test-curves, ark-vesta, ark-ed-on-bls12-381

  • No readme property

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

• ark-linear-sumcheck

  • Dependency blake2 0.9 is significantly outdated

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

    blake2 versions

  • Dependency hashbrown 0.14.0 is significantly outdated

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

    hashbrown versions

  • Dependency ark-ff 0.4.0 is slightly outdated

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

    ark-ff versions

  • Dependency ark-poly 0.4.0 is slightly outdated

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

    ark-poly versions

  • Dependency ark-serialize 0.4.0 is slightly outdated

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

    ark-serialize versions

  • Dependency ark-std 0.4.0 is slightly outdated

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

    ark-std versions

  • Imprecise dependency requirement rayon = 1

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

    rayon versions

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

    Crate features

• ark-relations

  • Dependency tracing-subscriber 0.2 is significantly outdated

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

    tracing-subscriber versions

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

    Crate features

• ark-ed-on-bn254

  • 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

• ark-curve-constraint-tests, ark-mnt6-753, ark-ed-on-cp6-782, ark-ed-on-bw6-761, ark-ed-on-mnt4-753, ark-ed-on-mnt4-298, ark-mnt4-753, ark-mnt6-298, ark-mnt4-298, ark-cp6-782, ark-ff-asm, ark-serialize-derive, ark-ff-macros

  • No readme property

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

• ark-std

  • Dependency colored 2 is a bit outdated

    Consider upgrading to 3.0.0 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.

    colored versions

  • Dependency rand 0.8 is a bit outdated

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

    rand versions

• ark-ff, ark-ec, ark-poly

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

    Crate features

• ark-ec

  • 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

• ark-serialize

  • Optional dependency 'ark-serialize-derive' 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-serialize-derive', 'rayon' may have been unintentional.

    Crate features

• ark-bls12-377, ark-bn254, ark-ed-on-bn254, ark-pallas, ark-vesta, ark-ed-on-bls12-381

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

    Crate features

• ark-std, ark-groth16, ark-snark, ark-relations, ark-crypto-primitives

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

    Use OR instead of /.

    SPDX license list

• ark-groth16

  • Optional dependency 'rayon' 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 'rayon', 'ark-r1cs-std', 'tracing', 'derivative' may have been unintentional.

    Crate features

• ark-gm17

  • Dependency ark-crypto-primitives ^0.3.0 is significantly outdated

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

    ark-crypto-primitives versions

  • Dependency ark-ec ^0.3.0 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.3.0 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.3.0 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.3.0 is significantly outdated

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

    ark-serialize versions

  • Dependency ark-std ^0.3.0 is significantly outdated

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

    ark-std versions

  • Dependency ark-r1cs-std ^0.3.0 is outdated

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

    ark-r1cs-std versions

  • Dependency ark-relations ^0.3.0 is significantly outdated

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

    ark-relations versions

  • Imprecise dependency requirement rayon = 1

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

    rayon 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

• ark-ed-on-bls12-377

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

• ark-mnt6-753, ark-ed-on-cp6-782, ark-ed-on-mnt4-753, ark-ed-on-mnt4-298, ark-mnt4-753, ark-mnt6-298, ark-mnt4-298

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

    Crate features

• ark-r1cs-std, ark-linear-sumcheck, ark-gm17, ark-nonnative-field

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

    Use OR instead of /.

    SPDX license list

• ark-cp6-782

  • Dependency itertools 0.10 is outdated

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

    itertools versions

• ark-nonnative-field

  • Dependency ark-ec ^0.3.0 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.3.0 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-std ^0.3.0 is significantly outdated

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

    ark-std versions

  • Dependency ark-r1cs-std ^0.3.0 is outdated

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

    ark-r1cs-std versions

  • Dependency ark-relations ^0.3.0 is significantly outdated

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

    ark-relations versions

  • Imprecise dependency requirement derivative = 2

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

    derivative versions

No issues found in: ark-algebra-test-templates

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