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.

• stdio-override

  • Published crate doesn't match its repository

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

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

    • Cargo.lock not found.

    Fetched https://github.com/elichai/stdio-override.git a5c0a7776bbf57e15e16712c9318af37c3bd5c56.

    Checked on 2025-02-02

    This check is experimental.

    Forum thread

• stdio-override, log-derive, worst-executor, random-trait, random-fast-rng, bits128, lorenz, two-party-hash

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

    Use OR instead of /.

    SPDX license list

• curv-kzen

  • Dependency digest 0.9 is significantly outdated

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

    digest versions

  • Dependency hmac 0.11 is significantly outdated

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

    hmac versions

  • Dependency p256 0.11.1 is significantly outdated

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

    p256 versions

  • Dependency rand 0.6 is significantly outdated

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

    rand versions

  • Dependency rand 0.7 is significantly outdated

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

    rand versions

  • Dependency secp256k1 0.20 is significantly outdated

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

    secp256k1 versions

  • Dependency sha2 0.8 is significantly outdated

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

    sha2 versions

  • Dependency sha2 0.9 is significantly outdated

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

    sha2 versions

  • Dependency sha3 0.9 is significantly outdated

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

    sha3 versions

  • Dependency cryptoxide 0.1.2 is significantly outdated

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

    cryptoxide versions

  • Dependency curve25519-dalek 3 is outdated

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

    curve25519-dalek 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

  • Dependency thiserror 1 is a bit outdated

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

    thiserror versions

  • Imprecise dependency requirement curve25519-dalek = 3

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

    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.

    curve25519-dalek 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 = ["elliptic-curve", "zero-knowledge-proofs", "curv"] (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.

• getrandom_package

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

  • The Cargo package has no git commit information

    Before publishing a package, make sure all packaged files are committed to the repository, and there are no "dirty" files. Push this commit to crate's public repository.

    To protect against supply chain attacks similar to CVE-2024-3094, lib.rs will soon start flagging non-reproducible packages without public source code as suspicious. Currently only git repositories are supported (but may be hosted anywhere, not just GitHub). If you'd like a different SCM supported, please file a feature request.

    More info

  • Missing keywords

    Help users find your crates. Add keywords = ["temp", "package", "getrandom"] (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.

• log-derive

  • Dependency darling 0.10.0 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.0.5 is significantly outdated

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

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

    If the crate is truly stable, why not make a 1.0.0 release?

    Maintenance status field docs

• lorenz

  • Dependency structopt 0.2 has issues

    It has been losing active users, which may be a sign it's deprecated or obsolete. Consider replacing it with a different crate.

    structopt crate

  • Dependency rand_os 0.1.3 has issues

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

    rand_os crate

  • Dependency ring 0.14.6 is significantly outdated

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

    ring versions

  • Dependency x25519-dalek 0.5.2 is significantly outdated

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

    x25519-dalek versions

  • Dependency zeroize 0.9.1 is significantly outdated

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

    zeroize versions

  • The Cargo package has no git commit information

    Before publishing a package, make sure all packaged files are committed to the repository, and there are no "dirty" files. Push this commit to crate's public repository.

    More info

• worst-executor

  • Latest stable release is old

    It's been over 2 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").

    Nightly crates tend to have a short lifespan. We're delisting them if they're not updated frequently.

    Maintenance status field docs

• random-trait

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

• log-derive, random-trait, random-fast-rng, getrandom_package

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

• two-party-hash

  • Dependency structopt 0.2.18 has issues

    It has been losing active users, which may be a sign it's deprecated or obsolete. Consider replacing it with a different crate.

    structopt crate

  • Dependency rand_os 0.2.0 has issues

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

    rand_os crate

• bits128

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

    Maintenance status field docs

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["bits128", "byte", "bit"] (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.

• random-trait, random-fast-rng, getrandom_package, lorenz, two-party-hash

  • 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

• derive_wrapper

  • Dependency quote 0.6 is significantly outdated

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

    quote versions

  • Dependency syn 0.15 is significantly outdated

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

    syn 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

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

    Use OR instead of /.

    SPDX license list

• derive_wrapper, sodot-ed25519, sodot-ot, sodot, sodot-ed448, sodot-tss, sodot-bls, sodot-eddsa, sodot-ecdsa

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

• sodot-ed25519, sodot-ot, sodot

  • Crate is 'reserved'

    Please be respectful of crates.io and don't squat crate names.

    It's OK if you intend to publish this project in the near future. Keep in mind that even if you have good intentions, things may not go as planned. crates.io won't reclaim abandoned crates, so reserving good names may end up wasting the good names.

• sodot-ed448, sodot-tss, sodot-bls, sodot-eddsa, sodot-ecdsa

  • Crate contains junk files

    The crate contains boilerplate Rust files with no real functionality.

• linux-sys

  • Internal error

    We couldn't check this crate at this time, because: Crate needed for the dashboard Origin( lib.rs/crates/linux-sys ). Please try again later.

No issues found in: kaspa-miner zk-paillier bitsign

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