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.

• sphinx-packet

  • Dependency blake2 0.8.0 is significantly outdated

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

    blake2 versions

  • Published crate doesn't match its repository

    Partially verified 36 files (includes 3 Cargo-generated).

    Files in the crates.io crate compared to the repository:

    • Cargo.lock not found.

    Fetched https://github.com/nymtech/sphinx.git 9955d64a304c5c24deaa9f2720357d0243852228.

    Checked on 2025-04-09

    This check is experimental.

    Forum thread

  • Dependency chacha 0.3.0 is slightly outdated

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

    chacha versions

  • Dependency rand 0.8.5 is a bit outdated

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

    rand versions

  • Dependency rand_distr 0.4.3 is a bit outdated

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

    rand_distr versions

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["cryptography"] 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 = ["sphinx", "sphinx-packet", "hmac"] (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.

• nym-pemstore

  • Failed to verify create's content against its repository

    Partially verified 5 files (includes 2 Cargo-generated).

    • warning: Crate tarball has been published from a different commit than the commit tagged by git tag 'v0.3.0'.
      • Create git tags after comitting any changes, and commit changes after bumping versions and running cargo update.

    Looked for the crate in common/pemstore/. Fetched https://github.com/nymtech/nym.git 8f3d7606f59c06bb44dc5b7d7275a7ba90305755.

    Checked on 2024-08-10

    Forum thread

  • Dependency pem 0.8 is significantly outdated

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

    pem versions

  • Missing keywords

    Help users find your crates. Add keywords = ["nym-pemstore", "format", "nym", "zero-knowledge", "platform"] (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.

• nym-bin-common

  • Dependency opentelemetry 0.19.0 is significantly outdated

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

    opentelemetry versions

  • Dependency opentelemetry-jaeger 0.18.0 has issues

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

    opentelemetry-jaeger crate

  • Dependency semver 0.11 is significantly outdated

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

    semver versions

  • Dependency tracing-opentelemetry 0.19.0 is significantly outdated

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

    tracing-opentelemetry versions

  • Dependency vergen =7.4.3 is significantly outdated

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

    vergen versions

  • Locked dependency version vergen =7.4.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.

    vergen versions

  • 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 pretty_env_logger 0.4.0 is outdated

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

    pretty_env_logger versions

  • Dependency tracing-tree 0.2.2 is outdated

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

    tracing-tree versions

  • Failed to verify create's content against its repository

    Partially verified 10 files (includes 2 Cargo-generated).

    • warning: Crate tarball has been published from a different commit than the commit tagged by git tag 'v0.6.0'.
      • Create git tags after comitting any changes, and commit changes after bumping versions and running cargo update.

    Looked for the crate in common/bin-common/. Fetched https://github.com/nymtech/nym.git 2032b3bdaee10faf6bc4080ef6a93ea3390480f5.

    Checked on 2024-07-28

    Forum thread

  • Missing keywords

    Help users find your crates. Add keywords = ["nym-bin-common", "binaries", "bin", "information", "platform"] (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 'opentelemetry-jaeger' 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 'opentelemetry-jaeger', 'tracing-opentelemetry', 'tracing-tree', 'serde_json', 'opentelemetry', 'tracing-subscriber' may have been unintentional.

    Crate features

• nym-sphinx-types, nym-pemstore, nym-bin-common

  • Missing categories

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

    List of available categories

• nym-sphinx-types

  • Dependency sphinx-packet 0.1.0 is slightly outdated

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

    sphinx-packet versions

  • Missing keywords

    Help users find your crates. Add keywords = ["nym-sphinx-types", "sphinx", "nym", "platform", "mix"] (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.

• nym-crypto, nym-mixnet-contract, nym-contracts-common, nym-mixnet-contract-common, nym-vesting-contract, nym-vesting-contract-common

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

• nym-sphinx-types, nym-pemstore, nym-bin-common

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

• lioness-rs

  • Dependency cipher 0.3.0 is outdated

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

    cipher versions

  • Dependency generic-array 0.14 is slightly outdated

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

    generic-array 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

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