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.

• rust-s3

  • Dependency aws-region 0.26 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.

    aws-region versions

  • Dependency quick-xml 0.36 is significantly outdated

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

    quick-xml versions

  • Imprecise dependency requirement async-std = 1

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

    async-std versions

  • Latest prerelease is old

    It's been over 5 months. 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

  • Optional dependency 'async-std' 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-std', 'futures', 'minidom', 'tokio', 'surf', 'reqwest', 'attohttpc', 'tokio-stream', 'block_on_proc' may have been unintentional.

    Crate features

• rust-s3, aws-region, aws-creds, nym-outfox

  • 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

• bigtable

  • Dependency goauth 0.6 is significantly outdated

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

    goauth versions

  • Dependency rustc-serialize 0.3.24 has issues

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

    rustc-serialize crate

  • Dependency smpl_jwt 0.4 is significantly outdated

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

    smpl_jwt 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 protobuf 2.8.1 is a bit outdated

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

    protobuf versions

• goauth

  • Latest prerelease is old

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

  • Imprecise dependency requirement arc-swap = 1

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

    arc-swap versions

• rust-hashcash

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

  • Dependency sha-1 0.8.2 has issues

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

    sha-1 crate

  • Dependency sha3 0.8.2 is significantly outdated

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

    sha3 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

  • 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

• aws-creds

  • Imprecise dependency requirement serde = 1

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

  • Dependency quick-xml 0.32 is outdated

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

    quick-xml versions

  • Missing categories

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

    List of available categories

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

    Crate features

• aws-region

  • Imprecise dependency requirement serde = 1

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

    serde versions

  • Missing categories

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

    List of available categories

• rust-s3, goauth, bigtable

  • Missing categories

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

    List of available categories

• protobuf-json-temp

  • README missing from the repository

    We've searched https://github\.com/mrjones/rust\-protobuf\-json\.git and could not find a README file there.

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

  • Dependency protobuf ^2.0 is a bit outdated

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

    protobuf versions

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["protobuf", "json", "serialization", "objects", "google"] (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-outfox

  • Could not fetch repository

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

  • 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

  • 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

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

  • Dependency curve25519-dalek 3.2 is outdated

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

    curve25519-dalek versions

  • Dependency getrandom 0.2.10 is outdated

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

    getrandom versions

  • Dependency sphinx-packet 0.1.0 is slightly outdated

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

    sphinx-packet versions

  • Missing keywords

    Help users find your crates. Add keywords = ["nym", "privacy", "package", "anonymous", "format"] (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.

• smpl_jwt

  • Dependency base64 0.21 is outdated

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

    base64 versions

  • Missing categories

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

    List of available categories

• rust-flatten-json, nym-outfox, pbuf

  • Missing categories

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

    List of available categories

• bigtable, rust-flatten-json, protobuf-json-temp, xx-bloomfilter

  • 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

• rust-flatten-json

  • Dependency error-chain ^0.12 has issues

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

    error-chain crate

• xx-bloomfilter

  • 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 bit-vec ^0.6 is outdated

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

    bit-vec versions

  • Dependency twox-hash ^1.4 is slightly outdated

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

    twox-hash versions

  • Missing categories

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

    List of available categories

• block_on_proc

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

• pbuf

  • Dependency byteorder 0.5.3 is significantly outdated

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

    byteorder versions

  • Dependency protobuf 1.0.22 is significantly outdated

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

    protobuf 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

• simpl

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["error", "own", "construction", "conversion", "lib"] (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.

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