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.

• testcontainers, jsonrpc_client, siren-types, tc_cli_client

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

    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

• testcontainers

  • Dependency etcetera 0.8.0 is slightly outdated

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

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

    etcetera versions

  • Dependency parse-display 0.9.0 is outdated

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

    parse-display versions

  • Optional dependency 'conquer-once' 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 'conquer-once', 'reqwest', 'signal-hook', 'serde-java-properties' may have been unintentional.

    Crate features

• libp2p-websocket-websys

  • 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

  • No readme property

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

• jsonrpc_client

  • Dependency isahc 0.9 is significantly outdated

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

    isahc versions

  • Buggy README path

    The non-local path to readme specified as \.\./README\.md exposes a bug in Cargo. Please use a path inside the crate's directory. Symlinks are okay. Please verify the change doesn't break any repo-relative URLs in the README.

  • Dependency reqwest 0.11 is outdated

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

    reqwest 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

• impl-template

  • Latest prerelease 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").

    Users pay attention to the latest release date. Even if the crate is perfectly fine as-is, users may not know that.

    Maintenance status field docs

  • Dependency itertools 0.8 is significantly outdated

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

    itertools versions

  • Dependency syn 1.0 is significantly outdated

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

    syn versions

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

    Use OR instead of /.

    SPDX license list

• base58-monero, monero

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

• jsonrpc_client, tc_core, tc_cli_client, tc_parity_parity

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

• libp2p-stream

  • Dependency rand 0.8 is a bit outdated

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

    rand versions

• xtra

  • Dependency event-listener 2.4.0 is outdated

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

    event-listener versions

  • Dependency smol 1.1 is outdated

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

    smol versions

• tc_core, tc_cli_client, tc_parity_parity

  • Could not fetch repository

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

• base58m, monero-epee-bin-serde, tc_trufflesuite_ganachecli, tc_coblox_bitcoincore, bitcoin_rpc_client

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

• siren-types

  • Dependency http 0.2 is outdated

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

    http versions

  • Latest stable release is old

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

• tc_core, tc_cli_client, tc_parity_parity

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

    Maintenance status field docs

• jsonrpc_client_macro

  • Dependency syn 1 is significantly outdated

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

    syn versions

  • Imprecise dependency requirement syn = 1

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

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

• tc_generic, tc_dynamodb_local, tc_elasticmq, tc_postgres

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

    Maintenance status field docs

• libp2p-websys-websocket

  • Crate contains junk files

    The crate contains boilerplate Rust files with no real functionality.

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

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