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.

• arti

  • Dependency notify 7 is significantly outdated

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

    notify versions

  • Optional dependency 'tor-rpc-connect' 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 'tor-rpc-connect', 'arti-rpcserver', 'visibility', 'rustls-crate', 'derive-deftly', 'dialoguer', 'hickory-proto', 'tokio-crate', 'secmem-proc', 'tor-rpcbase', 'async-ctrlc', 'tor-hsrproxy', 'tor-hsservice', 'signal-hook', 'tracing-journald', 'signal-hook-async-std', 'tokio-util' may have been unintentional.

    Crate features

• slotmap-careful, tor-consdiff, tor-ptmgr, equix, tor-cert, tor-dirclient

  • Imprecise dependency requirement thiserror = 2

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

    thiserror versions

• fs-mistrust, tor-rpcbase, tor-circmgr

  • Imprecise dependency requirement once_cell = 1

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

    once_cell versions

• fs-mistrust

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

    Crate features

• arti, arti-client, tor-keymgr, tor-guardmgr, tor-config, tor-rpcbase, tor-rtmock, tor-hsservice, tor-linkspec, tor-bytes, tor-socksproto, tor-hsclient

  • Dependency derive-deftly 0.14 is a bit outdated

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

    derive-deftly versions

• arti, arti-client, tor-keymgr, tor-guardmgr, tor-rtmock, tor-hsservice, tor-checkable, tor-log-ratelim

  • Imprecise dependency requirement humantime = 2

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

    humantime versions

• arti-client

  • Optional dependency 'visibility' 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 'visibility', 'dyn-clone', 'tor-geoip', 'tor-ptmgr', 'tor-rpcbase', 'tor-hsclient', 'anyhow', 'tor-hsservice', 'tor-hscrypto' may have been unintentional.

    Crate features

• arti-hyper

  • Dependency arti-client 0.19.0 is significantly outdated

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

    arti-client versions

  • Dependency tor-error 0.19.0 is significantly outdated

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

    tor-error versions

  • Dependency tor-rtcompat 0.19.0 is significantly outdated

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

    tor-rtcompat versions

  • Dependency hyper 0.14 is outdated

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

    hyper versions

  • Dependency thiserror 1 is a bit outdated

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

    thiserror versions

  • Dependency tls-api 0.9.0 is outdated

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

    tls-api versions

  • Dependency tls-api-native-tls 0.9.0 is outdated

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

    tls-api-native-tls versions

• tor-llcrypto

  • 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

  • Dependency der-parser 9 is outdated

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

    der-parser versions

  • Dependency getrandom 0.2.3 is outdated

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

    getrandom versions

  • Imprecise dependency requirement signature = 2

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

    signature versions

  • Optional dependency 'derive-deftly' 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 'derive-deftly', 'openssl', 'typenum', 'tor-memquota', 'cipher' may have been unintentional.

    Crate features

• tor-config

  • Dependency notify 7 is significantly outdated

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

    notify versions

  • Imprecise dependency requirement either = 1

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

    either versions

• tor-units

  • 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

  • Dependency derive-deftly 0.14.2 is a bit outdated

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

    derive-deftly versions

  • Optional dependency 'derive-deftly' 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 'derive-deftly', 'tor-memquota' may have been unintentional.

    Crate features

• tor-chanmgr, tor-protover, tor-persist, hashx, tor-hsrproxy, tor-basic-utils, tor-units, tor-rpc-connect, tor-geoip, fslock-guard, arti-rpc-client-core, tor-general-addr

  • Imprecise dependency requirement thiserror = 2

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

• tor-netdoc

  • Dependency hex-literal 0.4 is outdated

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

    hex-literal versions

  • Imprecise dependency requirement bitflags = 2

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

  • Optional dependency 'hex-literal' 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-literal', 'tor-hscrypto', 'visibility', 'rand', 'tor-units', 'visible', 'tor-linkspec' may have been unintentional.

    Crate features

• arti-relay

  • Dependency derive_more 1.0.0 is outdated

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

    derive_more versions

  • Dependency directories 5 is outdated

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

    directories versions

  • Dependency rand 0.8.5 is a bit outdated

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

    rand versions

  • Dependency strum 0.26.3 is outdated

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

    strum versions

• tor-rtcompat

  • Imprecise dependency requirement pin-project = 1

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

    pin-project versions

  • Optional dependency 'async-native-tls' 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 'async-native-tls', 'async-io', 'rustls-pki-types', 'async-std-crate', 'native-tls-crate', 'x509-signature', 'tokio-crate', 'futures-rustls', 'tokio-util', 'arbitrary' may have been unintentional.

    Crate features

• tor-netdir

  • Dependency typed-index-collections ~3.1.0 is outdated

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

    typed-index-collections versions

  • Imprecise dependency requirement bitflags = 2

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

  • Optional dependency 'visibility' 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 'visibility', 'digest', 'tor-geoip', 'hex', 'postage', 'tor-hscrypto', 'time' may have been unintentional.

    Crate features

• tor-dirmgr

  • Dependency rusqlite 0.32.1 is outdated

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

    rusqlite versions

  • Imprecise dependency requirement event-listener = 5

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

    event-listener versions

  • Optional dependency 'memmap2' 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 'memmap2', 'tor-geoip' may have been unintentional.

    Crate features

• tor-proto

  • Imprecise dependency requirement bytes = 1

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

    bytes versions

  • Optional dependency 'tor-hscrypto' 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 'tor-hscrypto', 'visibility', 'tokio-crate', 'tokio-util' may have been unintentional.

    Crate features

• tor-cell

  • Imprecise dependency requirement bitflags = 2

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

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

    Crate features

• tor-bytes

  • Dependency getrandom 0.2.3 is outdated

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

    getrandom versions

  • Imprecise dependency requirement bytes = 1

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

    bytes versions

• tor-hscrypto

  • Imprecise dependency requirement signature = 2

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

    signature versions

  • Optional dependency 'arrayvec' 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 'arrayvec', 'tor-memquota', 'zeroize', 'derive-deftly', 'equix', 'blake2', 'cipher' may have been unintentional.

    Crate features

• arti-client, tor-rtcompat, tor-guardmgr, tor-config, tor-proto, tor-netdoc, tor-circmgr, tor-rtmock, tor-hsservice, tor-cell, tor-bytes, tor-socksproto, tor-llcrypto, tor-hsclient

  • Dependency educe 0.4.6 is outdated

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

    educe versions

• arti-client, tor-keymgr, tor-guardmgr, tor-proto, tor-netdoc, tor-circmgr, tor-cell, tor-hscrypto, tor-hsclient

  • Dependency rand 0.8 is a bit outdated

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

    rand versions

• arti-client, tor-rtcompat, tor-keymgr, tor-guardmgr, tor-proto, tor-rpcbase, tor-netdoc, tor-circmgr, tor-rtmock, tor-hsservice, tor-linkspec, tor-cell, tor-cert, tor-dirclient, tor-llcrypto, tor-hscrypto, tor-hsclient

  • Dependency derive_more 1.0.0 is outdated

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

    derive_more versions

• derive-deftly

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["development-tools::procedural-macro-helpers"] 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

  • Missing keywords

    Help users find your crates. Add keywords = ["macro-derive", "proc-macro", "macro-expansion", "write", "data"] (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.

• tor-keymgr

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

    Crate features

• tor-guardmgr

  • Optional dependency 'tor-protover' 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 'tor-protover', 'tor-rtmock' may have been unintentional.

    Crate features

• tor-guardmgr, tor-config, tor-rtmock, tor-hsservice, tor-linkspec, tor-hsclient

  • Dependency strum 0.26.3 is outdated

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

    strum versions

• tor-basic-utils

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

• tor-proto, tor-hsservice, tor-llcrypto

  • Dependency rand_core 0.6.2 is a bit outdated

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

    rand_core versions

• tor-proto, tor-cell, tor-llcrypto, tor-hscrypto

  • Dependency derive-deftly 0.14.2 is a bit outdated

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

    derive-deftly versions

• tor-circmgr

  • Optional dependency 'visibility' 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 'visibility', 'tor-geoip' may have been unintentional.

    Crate features

• tor-config-path

  • Dependency directories 5 is outdated

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

    directories versions

  • Optional dependency 'shellexpand' 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 'shellexpand', 'directories', 'tor-general-addr' may have been unintentional.

    Crate features

• tor-ptmgr

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

    Crate features

• tor-hsservice

  • Dependency rand 0.8.5 is a bit outdated

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

    rand versions

• tor-linkspec

  • Imprecise dependency requirement by_address = 1

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

    by_address versions

• avltree

  • Missing categories

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

    List of available categories

  • 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 rand 0.3 is significantly outdated

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

    rand versions

  • Latest stable release is old

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

  • Missing keywords

    Help users find your crates. Add keywords = ["tree", "avl", "node", "index", "iterator"] (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.

• tor-cert

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

    Crate features

• tor-dirclient

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

    Crate features

• tor-socksproto

  • 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

• tor-hsclient

  • Imprecise dependency requirement either = 1

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

    either versions

• tor-error

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

    Crate features

• tor-error, tor-netdir, tor-dirmgr

  • Dependency strum 0.26.3 is outdated

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

    strum versions

• tor-error, arti-relay, tor-config-path

  • Imprecise dependency requirement once_cell = 1

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

    once_cell versions

• tor-error, tor-chanmgr, safelog, test-temp-dir, tor-netdir, tor-persist, tor-dirmgr, tor-basic-utils, tor-units, tor-rpc-connect, tor-memquota, tor-geoip, arti-rpcserver, arti-rpc-client-core, tor-key-forge, tor-general-addr, tor-relay-crypto

  • Dependency derive_more 1.0.0 is outdated

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

    derive_more versions

• tor-async-utils, tor-memquota, arti-hyper

  • Imprecise dependency requirement pin-project = 1

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

    pin-project versions

• tor-async-utils, tor-persist, tor-hsrproxy, tor-memquota, arti-rpcserver, tor-key-forge, tor-relay-crypto

  • Dependency derive-deftly 0.14 is a bit outdated

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

    derive-deftly versions

• tor-async-utils, tor-chanmgr, safelog, test-temp-dir, tor-dirmgr, tor-memquota, arti-rpc-client-core, arti-hyper

  • Dependency educe 0.4.6 is outdated

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

    educe versions

• tor-chanmgr, tor-netdir, tor-relay-selection, tor-dirmgr, tor-basic-utils, tor-rpc-connect, arti-rpcserver, tor-key-forge

  • Dependency rand 0.8 is a bit outdated

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

    rand versions

• safelog

  • Imprecise dependency requirement either = 1

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

    either versions

• test-temp-dir

  • Imprecise dependency requirement tempfile = 3

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

    tempfile versions

• tor-persist

  • Optional dependency 'fslock-guard' 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 'fslock-guard', 'amplify' may have been unintentional.

    Crate features

• tor-relay-selection

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

    Crate features

• arti-rpc-client-core

  • Dependency rand 0.8.5 is a bit outdated

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

    rand versions

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

    Crate features

• hashx

  • Dependency rand_core 0.6.4 is a bit outdated

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

    rand_core versions

• fixed-capacity-vec

  • Missing keywords

    Help users find your crates. Add keywords = ["fixed-size", "heap", "data-structures", "compile-time", "length"] (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.

  • Using outdated edition for no reason

    We estimate that this crate requires at least Rust 1.58, which is newer than the last 2018-edition compiler. You can upgrade without breaking any compatibility. Run cargo fix --edition and update edition="…" in Cargo.toml.

    Using the latest edition helps avoid old quirks of the compiler, and ensures Rust code has consistent syntax and behavior across all projects.

    The Edition Guide

• tor-rpc-connect

  • Optional dependency 'fslock-guard' 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 'fslock-guard', 'tor-rtcompat' may have been unintentional.

    Crate features

• tor-memquota

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

    Crate features

• arti-rpcserver

  • Imprecise dependency requirement bytes = 1

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

    bytes versions

• tor-key-forge

  • Imprecise dependency requirement signature = 2

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

    signature versions

• tor-general-addr

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

    Crate features

• tor-relay-crypto

  • Imprecise dependency requirement humantime = 2

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

    humantime versions

No issues found in: retry-error caret oneshot-fused-workaround

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