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.

• rocksdb

  • Dependency librocksdb-sys 0.17.1 is significantly outdated

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

    librocksdb-sys versions

  • Imprecise dependency requirement serde = 1

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

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

    Crate features

• exonum_sodiumoxide, exonum_libsodium-sys, exonum_rocksdb

  • 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

• librocksdb-sys

  • Dependency bindgen 0.59 is significantly outdated

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

    bindgen versions

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

    Use OR instead of /.

    SPDX license list

  • Published crate contains binary files

    The crate contains binary files (obscure autoconf code). Crates are meant to be compiled from source. Please check that you haven't published temporary build files by accident. If you have test fixtures, consider excluding them from crates-io tarball, since Cargo doesn't run tests from crates-io packages.

    Audit page

• exonum_rocksdb

  • 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 tempdir 0.3 has issues

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

    tempdir crate

  • Latest stable release is old

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

• exonum_libsodium-sys

  • Dependency zip 0.5 is outdated

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

    zip versions

  • Imprecise dependency requirement cc = 1

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

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

    Maintenance status field docs

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

• exonum_sodiumoxide

  • 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

• protobuf-convert

  • Dependency darling 0.14 is significantly outdated

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

    darling versions

  • Dependency syn 1 is significantly outdated

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

    syn versions

  • Imprecise dependency requirement serde = 1

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

  • Dependency heck 0.4 is outdated

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

    heck versions

  • Imprecise dependency requirement protobuf-codegen = 3

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

    protobuf-codegen versions

No issues found in: aurora-evm aurora-engine-sdk aurora-engine-precompiles aurora-engine-transactions aurora-engine-modexp aurora-engine-types pwbox exonum exonum-build exonum-btc-anchoring exonum-time exonum-cli exonum-explorer-service exonum-supervisor exonum-system-api exonum-middleware-service exonum-testkit exonum-explorer exonum-node exonum-rust-runtime exonum-keys exonum-merkledb exonum-crypto exonum-api exonum-proto exonum-derive btc-transaction-utils exonum-cryptocurrency-advanced exonum-configuration exonum_jsonrpc exonum_librocksdb-sys exonum_bitcoinrpc

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