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.

• corro-speedy

  • Dependency memoffset 0.8 is significantly outdated

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

    memoffset versions

  • Dependency speedy-derive = 0.8.6 is significantly outdated

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

    speedy-derive 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 glam >= 0.15, <= 0.24 is outdated

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

    glam versions

  • Dependency indexmap 1 is outdated

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

    indexmap versions

  • Failed to verify create's content against its repository

    Verified 29 out of 31 files (includes 1 Cargo-generated).

    • warning: The crates.io package has no commit hash associated with it.
      • Publish a new version, without using --allow-dirty flag. Make sure all changes are committed before publishing. Use include/exclude in Cargo.toml to omit unnecessary files.
    • warning: The crates.io package has no information about its path inside its repository.
    • warning: Could not find Cargo.toml for this package in its repo (via tags).
    • warning: Could not discover crate's location in its repository (via tags).

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

    • Cargo.toml.orig does not match the repository.
    • settings.json not found.

    Fetched https://github.com/koute/speedy.git c0f715d3b16758f4a1d278e7affbd3e7bb9f1ff7.

    Checked on 2024-07-28

    This check is experimental.

    Forum thread

  • Imprecise dependency requirement indexmap = 1

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

    indexmap versions

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

    Use OR instead of /.

    SPDX license list

• tripwire

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

  • Latest prerelease is old

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

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

  • 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

  • Imprecise dependency requirement tokio = 1

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

    tokio versions

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["asynchronous"] 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 = ["future", "complete", "shutdown", "pre-emptible", "graceful-shutdown"] (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.

• fly-accept-encoding

  • Dependency http 0.2 is outdated

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

    http versions

  • Dependency itertools 0.10 is outdated

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

    itertools versions

  • Dependency thiserror 1.0 is a bit outdated

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

    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.

• corro-client

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

  • Latest prerelease is old

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

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

  • 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

  • Dependency bb8 0.8.0 is a bit outdated

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

    bb8 versions

  • Dependency compact_str 0.7.0 is outdated

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

    compact_str versions

  • Dependency hyper 0.14.26 is outdated

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

    hyper versions

  • Dependency rusqlite 0.29.0 is outdated

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

    rusqlite versions

  • Dependency thiserror 1.0.40 is a bit outdated

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

    thiserror versions

  • Dependency tokio-serde 0.8 is a bit outdated

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

    tokio-serde versions

  • Imprecise dependency requirement tokio = 1

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

    tokio versions

  • Missing keywords

    Help users find your crates. Add keywords = ["corrosion", "interact", "client"] (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.

• corro-api-types

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

  • Latest prerelease is old

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

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

  • 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

  • Dependency bb8 0.8.0 is a bit outdated

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

    bb8 versions

  • Dependency compact_str 0.7.0 is outdated

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

    compact_str versions

  • Dependency rusqlite 0.29.0 is outdated

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

    rusqlite versions

  • Dependency thiserror 1.0.40 is a bit outdated

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

    thiserror versions

  • Imprecise dependency requirement tokio = 1

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

    tokio versions

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["api", "type", "corrosion"] (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.

• consul-client

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

  • Dependency hyper-rustls 0.24.0 is significantly outdated

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

    hyper-rustls versions

  • Latest prerelease is old

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

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

  • 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

  • Dependency hyper 0.14.26 is outdated

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

    hyper versions

  • Dependency rustls 0.21.0 is outdated

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

    rustls versions

  • Dependency rustls-pemfile 1.0.2 is outdated

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

    rustls-pemfile versions

  • Dependency serde_with 2.3.2 is outdated

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

    serde_with versions

  • Dependency thiserror 1.0.40 is a bit outdated

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

    thiserror versions

  • Missing keywords

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

• quinn-plaintext

  • Dependency quinn-proto 0.10 is outdated

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

    quinn-proto versions

  • Imprecise dependency requirement bytes = 1

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

    bytes versions

• corro-types

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

  • Latest prerelease is old

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

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

  • 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

  • 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 bb8 0.8.0 is a bit outdated

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

    bb8 versions

  • Dependency compact_str 0.7.0 is outdated

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

    compact_str versions

  • Dependency config 0.13.3 is outdated

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

    config versions

  • Dependency fallible-iterator 0.2.0 is outdated

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

    fallible-iterator versions

  • Dependency foca 0.12.0 is outdated

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

    foca versions

  • Dependency indexmap 1.9.3 is outdated

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

    indexmap versions

  • Dependency itertools 0.10.5 is outdated

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

    itertools versions

  • Dependency metrics 0.21.0 is outdated

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

    metrics versions

  • Dependency nom 7.1.3 is a bit outdated

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

    nom versions

  • Dependency rand 0.8.5 is a bit outdated

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

    rand versions

  • Dependency rusqlite 0.29.0 is outdated

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

    rusqlite versions

  • Dependency sqlite3-parser 0.8.0 is outdated

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

    sqlite3-parser versions

  • Dependency thiserror 1.0.40 is a bit outdated

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

    thiserror versions

  • Dependency uhlc 0.5.2 is outdated

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

    uhlc versions

  • Imprecise dependency requirement tokio = 1

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

    tokio versions

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["types", "corrosion", "corro-types"] (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.

• rhai-tpl

  • Dependency logos 0.13.0 is outdated

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

    logos versions

  • Dependency thiserror 1.0.44 is a bit outdated

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

    thiserror versions

• corrosive

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