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.

• benaloh-challenge

  • Imprecise dependency requirement thiserror = 1

    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

  • Dependency rand 0.8 is a bit 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.

    rand versions

  • Dependency rand_core 0.6 is a bit outdated

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

    rand_core versions

  • Dependency thiserror 1 is a bit outdated

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

    Easy way to bump dependencies: cargo install cargo-edit; cargo upgrade -i; Also check out Dependabot service on GitHub.

    thiserror versions

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

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

    Maintenance status field docs

• tallystick

  • Dependency failure 0.1.6 has issues

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

    failure crate

  • Dependency hashbrown 0.11.2 is significantly outdated

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

    hashbrown versions

  • Dependency derive_more 0.99.3 is outdated

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

    derive_more versions

  • Dependency petgraph 0.6.0 is a bit outdated

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

    petgraph versions

• gotenberg_pdf, tallyman, polars_gdal

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

• ecies-ed25519

  • Dependency aes-gcm 0.8.0 is significantly outdated

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

    aes-gcm versions

  • Dependency hkdf 0.10.0 is significantly outdated

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

    hkdf versions

  • Dependency sha2 0.9.3 is significantly outdated

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

    sha2 versions

  • Dependency curve25519-dalek 3.1.0 is outdated

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

    curve25519-dalek versions

  • Dependency ring 0.16.20 is outdated

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

    ring versions

  • Dependency thiserror 1.0.24 is a bit outdated

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

    thiserror versions

• rsa-fdh

  • Dependency num-bigint-dig 0.6 is significantly outdated

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

    num-bigint-dig versions

  • Dependency rsa 0.3.0 is significantly outdated

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

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

    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

  • Dependency fdh 0.7.3 is a bit outdated

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

    fdh versions

  • Dependency thiserror 1.0.22 is a bit outdated

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

    thiserror versions

• tallyman

  • 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

  • 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

  • Missing keywords

    Help users find your crates. Add keywords = ["election", "vote", "condorcet", "tally", "due"] (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.

• cryptoballot

  • Dependency aes-gcm 0.3.0 is significantly outdated

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

    aes-gcm versions

  • Dependency curve25519-dalek 2.0.0 is significantly outdated

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

    curve25519-dalek versions

  • Dependency digest 0.8.1 is significantly outdated

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

    digest versions

  • Dependency failure 0.1.6 has issues

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

    failure crate

  • Dependency hex 0.3.1 is significantly outdated

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

    hex versions

  • Dependency hkdf 0.8.0 is significantly outdated

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

    hkdf versions

  • Dependency num_enum 0.4.2 is significantly outdated

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

    num_enum versions

  • Dependency rsa 0.2.0 is significantly outdated

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

    rsa versions

  • Dependency sha2 0.8.1 is significantly outdated

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

    sha2 versions

  • Dependency sharks 0.3 is significantly outdated

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

    sharks versions

  • Dependency uuid 0.8.1 is significantly outdated

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

    uuid versions

  • Dependency ed25519-dalek 1.0.0-pre.3 is outdated

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

    ed25519-dalek versions

  • Dependency hex-buffer-serde 0.2 is outdated

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

    hex-buffer-serde versions

  • Dependency rsa-fdh 0.2.1 is outdated

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

    rsa-fdh versions

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["voting", "secure", "verifiable", "key", "vote"] (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.

• gotenberg_pdf

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["web-programming::http-client"] to the Cargo.toml.

    List of available categories

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

    Crate features

• tallystick, fdh, ecies-ed25519

  • 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

• fdh

  • Dependency num-bigint-dig 0.6 is significantly outdated

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

    num-bigint-dig versions

  • Dependency thiserror 1.0.23 is a bit outdated

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

    thiserror versions

• polars_gdal

  • Dependency polars 0.26 is significantly outdated

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

    polars versions

  • Imprecise dependency requirement thiserror = 1

    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

  • Dependency gdal 0.14 is outdated

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

    gdal versions

  • Dependency gdal-sys 0.8 is outdated

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

    gdal-sys versions

  • Dependency thiserror 1 is a bit outdated

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

    thiserror versions

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["polars", "gdal", "geospatial", "read-write", "postgis"] (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.

  • Published crate contains binary files

    The crate contains binary files (Zip file). 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

• rsa-fdh, fdh, ecies-ed25519

  • Dependency digest 0.9.0 is significantly outdated

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

    digest versions

• rsa-fdh, ecies-ed25519, cryptoballot

  • Dependency rand 0.7.3 is significantly outdated

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

    rand versions

• rsa-fdh, tallyman, cryptoballot

  • 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

• sidefuzz

  • 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

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