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.

• serde_cbor_2

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

    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

  • Dependency half 1.2.0 is outdated

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

    half versions

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

    Use OR instead of /.

    SPDX license list

• local-channel, local-waker, serde-bool, apple-security-framework, actix-limitation, apple-security-framework-sys, actix-ws-ng, double-int, actix-broker, actix-client-ip-cloudflare, actix-hash

  • 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

• actix-web-lab

  • Dependency http 0.2.7 is outdated

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

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

    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.

    bytes versions

  • Optional dependency 'actix-web-lab-derive' 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 'actix-web-lab-derive', 'actix-files', 'rmp-serde', 'serde_cbor_2' may have been unintentional.

    Crate features

• local-channel

  • Failed to verify create's content against its repository

    Partially verified 8 files (includes 2 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: Repository fetch error: missing delta bases; class=Indexer (15).
      • Ooops? If this shouldn't happen, file a bug https://gitlab.com/lib.rs/main

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

    • Cargo.toml.orig does not match the repository.

    Looked for the crate in local-channel/. Fetched https://github.com/actix/actix-net.git tagged local-channel-v0.1.5 (61b6e01b0224ef2eb6b96b6b8c1766bfbcac1787).

    Checked on 2024-07-24

    This check is experimental.

    Forum thread

  • 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

• bytesize

  • Imprecise dependency requirement arbitrary = 1

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

    arbitrary versions

• actix-test

  • Dependency rustls 0.22 is significantly outdated

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

    rustls versions

  • Dependency rustls 0.20 is outdated

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

    rustls versions

  • Dependency rustls 0.21 is outdated

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

    rustls versions

  • Imprecise dependency requirement actix-http-test = 3

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

    actix-http-test versions

  • Optional dependency 'tls-rustls-0_21' 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 'tls-rustls-0_21', 'tls-rustls-0_23', 'tls-openssl', 'tls-rustls-0_22', 'tls-rustls-0_20' may have been unintentional.

    Crate features

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

• oas3

  • Dependency serde_yaml 0.9.34-deprecated has issues

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

    serde_yaml crate

  • Dependency derive_more 1 is outdated

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

    derive_more versions

  • Imprecise dependency requirement http = 1

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

    http versions

• async-svc

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

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

  • 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

  • Missing keywords

    Help users find your crates. Add keywords = ["traits", "svc", "async-svc", "trait"] (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.

• confik, detrim, serde-bool, sparklepost, double-int

  • Imprecise dependency requirement serde = 1

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

• apple-security-framework

  • Failed to verify create's content against its repository

    Could not check any files

    • 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.
    • error: Repository doesn't exist: Can't checkout the repository. It's either gone or private: remote authentication required but no callback set; class=Http (34); code=Auth (-16).
      • Make sure the repository URL in Cargo.toml is correct and works with git clone. The repository must be public.

    Checked on 2024-07-28

    Forum thread

  • Dependency core-foundation 0.9.3 is a bit outdated

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

    core-foundation versions

  • Imprecise dependency requirement bitflags = 2

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

    bitflags versions

• async-compression

  • Imprecise dependency requirement memchr = 2

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

    memchr versions

  • Optional dependency 'zstd-safe' 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 'zstd-safe', 'bzip2', 'futures-io', 'libzstd', 'tokio', 'flate2', 'brotli' may have been unintentional.

    Crate features

  • Using outdated edition for no reason

    We estimate that this crate requires at least Rust 1.60, which is newer than the last 2018-edition compiler. You can upgrade without breaking any compatibility. Run cargo fix --edition and update edition="…" in Cargo.toml.

    Using the latest edition helps avoid old quirks of the compiler, and ensures Rust code has consistent syntax and behavior across all projects.

    The Edition Guide

• inspect-cert-chain

  • Dependency const-oid 0.9.6 is a bit outdated

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

    const-oid versions

  • Imprecise dependency requirement arboard = 3

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

    arboard versions

  • Missing categories

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

    List of available categories

• actix-limitation

  • Dependency actix-session 0.8 is significantly outdated

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

    actix-session versions

  • Dependency derive_more 0.99.7 is outdated

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

    derive_more versions

  • Dependency redis 0.23 is outdated

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

    redis versions

  • Failed to verify create's content against its repository

    Partially verified 12 files (includes 2 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.

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

    • Cargo.toml.orig does not match the repository.

    Looked for the crate in actix-limitation/. Fetched https://github.com/actix/actix-extras.git tagged limitation-v0.5.1 (6caf37ceddabd67d3451cc87158394c330d05c12).

    Checked on 2024-07-28

    Forum thread

  • Imprecise dependency requirement actix-web = 4

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

    actix-web versions

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

    Crate features

• cargo-ci-cache-clean

  • Imprecise dependency requirement walkdir = 2

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

    walkdir versions

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["development-tools::cargo-plugins", "development-tools::testing"] to the Cargo.toml.

    List of available categories

• apple-security-framework-sys

  • Failed to verify create's content against its repository

    Could not check any files

    • 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.
    • error: Repository doesn't exist: Can't checkout the repository. It's either gone or private: remote authentication required but no callback set; class=Http (34); code=Auth (-16).
      • Make sure the repository URL in Cargo.toml is correct and works with git clone. The repository must be public.

    Checked on 2024-08-10

    Forum thread

• impl-more, detrim

  • Using outdated edition for no reason

    We estimate that this crate requires at least Rust 1.56, which is newer than the last 2018-edition compiler. You can upgrade without breaking any compatibility. Run cargo fix --edition and update edition="…" in Cargo.toml.

    The Edition Guide

• tinymap

  • Dependency hashbrown 0.13 is significantly outdated

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

    hashbrown versions

  • 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 = ["stack", "tinymap", "tiny-map"] (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 'hashbrown' 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 'hashbrown' may have been unintentional.

    Crate features

  • Using outdated edition for no reason

    We estimate that this crate requires at least Rust 1.61, which is newer than the last 2018-edition compiler. You can upgrade without breaking any compatibility. Run cargo fix --edition and update edition="…" in Cargo.toml.

    The Edition Guide

• actix-ws, actix-settings, actix-hash

  • Imprecise dependency requirement actix-http = 3

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

    actix-http versions

• acme-rfc8555

  • Dependency rand 0.8 is a bit outdated

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

    rand versions

  • Imprecise dependency requirement rustls-pemfile = 2

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

    rustls-pemfile versions

• russe

  • Imprecise dependency requirement aho-corasick = 1

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

    aho-corasick versions

  • Missing categories

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

    List of available categories

• actix-multipart-derive

  • Imprecise dependency requirement parse-size = 1

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

    parse-size versions

• roast

  • Dependency colored 2 is a bit outdated

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

    colored versions

  • Dependency derive_more 1 is outdated

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

    derive_more versions

  • Imprecise dependency requirement http = 1

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

    http versions

• actix-settings

  • Dependency derive_more 0.99.7 is outdated

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

    derive_more versions

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["actix-web", "settings", "variables", "async"] (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.

• serde-bool

  • Failed to verify create's content against its repository

    Partially verified 23 files (includes 2 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.

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

    • Cargo.toml.orig does not match the repository.

    Fetched https://github.com/x52dev/serde-bool.git tagged serde-bool-v0.1.3 (68d57974a3b29568618aa7d26d85cc59d3603d1b).

    Checked on 2024-07-24

    Forum thread

• acme-lite

  • 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

  • Dependency rand 0.8 is a bit outdated

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

    rand versions

  • Dependency reqwest 0.11 is outdated

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

    reqwest versions

  • Imprecise dependency requirement once_cell = 1

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

    once_cell versions

• actix-ws-ng

  • Failed to verify create's content against its repository

    Partially verified 18 files (includes 3 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: There is no matching git tag containing version '0.3.0'.
    • warning: Had to perform fuzzy search of the head branch due to lack of commit information in the package.

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

    • Cargo.lock not found.
    • Cargo.toml.orig does not match the repository.

    Fetched https://github.com/robjtede/actix-ws-ng.git 55bfeca4a74c1c3d4a09bbd662b2b8dc1be23433.

    Checked on 2024-07-24

    Forum thread

  • Imprecise dependency requirement bytestring = 1

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

    bytestring versions

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

    Use OR instead of /.

    SPDX license list

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["actor", "message", "ok", "return", "actors"] (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.

• actix-broker

  • Dependency ahash 0.7 has issues

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

    ahash crate

  • Missing categories

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

    List of available categories

• confik-macros

  • Imprecise dependency requirement syn = 2

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

  • Published crate doesn't match its repository

    Partially verified 57 files (includes 4 Cargo-generated).

    • warning: Cargo.toml.orig from crates.io is not an exact match with the repository.

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

    • Cargo.lock not found.
    • Cargo.toml.orig does not match the repository.

    Looked for the crate in confik-macros/. Fetched https://github.com/x52dev/confik.git tagged confik-v0.13.0 (63ec8ac2131f146d8102cac58a11f3b30a6d1f21).

    Checked on 2025-03-16

    Forum thread

• actix-client-ip-cloudflare

  • Dependency ipnetwork 0.20 is a bit outdated

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

    ipnetwork versions

  • Failed to verify create's content against its repository

    Partially verified 14 files (includes 3 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: Repository fetch error: Broken repo: protocol error, missing OIDs.
      • Ooops? If this shouldn't happen, file a bug https://gitlab.com/lib.rs/main

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

    • Cargo.lock not found.
    • Cargo.toml.orig does not match the repository.

    Looked for the crate in actix-client-ip-cloudflare/. Fetched https://github.com/robjtede/actix-web-lab.git tagged client-ip-cloudflare-v0.2.0 (318567000ce167ce952bbbb52bb127c1f6b6b45e).

    Checked on 2024-07-24

    Forum thread

  • Imprecise dependency requirement actix-web = 4

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

    actix-web versions

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

    Crate features

• actix-web-lab-derive

  • Published crate doesn't match its repository

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

    • warning: Cargo.toml.orig from crates.io is not an exact match with the repository.

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

    • Cargo.lock not found.
    • Cargo.toml.orig does not match the repository.

    Looked for the crate in actix-web-lab-derive/. Fetched https://github.com/robjtede/actix-web-lab.git tagged lab-v0.24.0 (f1b994675202ab99cf85496bab08e3ecd15a1124).

    Checked on 2025-03-09

    Forum thread

  • Imprecise dependency requirement syn = 2

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

• sparklepost

  • License MPL-2.0+/LGPL-3.0+ is not in SPDX syntax

    Use OR instead of /.

    SPDX license list

• double-int

  • Failed to verify create's content against its repository

    Verified 18 out of 23 files (includes 2 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.

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

    • Cargo.toml.orig does not match the repository.
    • CHANGELOG.md does not match the repository.
    • README.md does not match the repository.
    • .github/workflows/
      • lint.yml does not match the repository.
      • coverage.yml does not match the repository.
      • ci.yml does not match the repository.

    Fetched https://github.com/x52dev/double-int.git tagged double-int-v0.1.0 (9ef10fb4e1a722b32bf2153bdae4f92e5f6b964d).

    Checked on 2024-08-04

    Forum thread

• actix-hash

  • Dependency actix-web-lab 0.19 is outdated

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

    actix-web-lab versions

  • Failed to verify create's content against its repository

    Partially verified 12 files (includes 3 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.

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

    • Cargo.lock not found.
    • Cargo.toml.orig does not match the repository.

    Looked for the crate in actix-hash/. Fetched https://github.com/robjtede/actix-web-lab.git tagged hash-v0.5.0 (e83d944837de4ee6cad221a1b2b4202a5a9b57da).

    Checked on 2024-07-24

    Forum thread

• rustversion-msrv

  • Using outdated edition for no reason

    We estimate that this crate requires at least Rust 1.63, which is newer than the last 2018-edition compiler. You can upgrade without breaking any compatibility. Run cargo fix --edition and update edition="…" in Cargo.toml.

    The Edition Guide

• doc-since

  • 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 syn 1 is significantly outdated

    Upgrade to 2.0.100 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.100". 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 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

• actix-multipart-derive-impl

  • Dependency syn 1 is significantly outdated

    Upgrade to 2.0.100 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.100". 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

  • 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

  • Buggy README path

    The non-local path to readme specified as \.\./README\.md exposes a bug in Cargo. Please use a path inside the crate's directory. Symlinks are okay. Please verify the change doesn't break any repo-relative URLs in the README.

• actix-multipart-derive-impl, protobug, actix-idempotency, http-status, flex, actix-client, actx-web, actx, http-fields, http-lite, qpack, actix-websockets, actix-websocket, actix-proxy-protocol, actix-client-ip, http-field, http-version, http-status-code, proxyproto, httpea, http-accept, http-method, actix-lab, actix-signature, actix-crypto, trix, actix-extras, actix-extra, tix, actix-web-test, robjtede

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

• protobug, khaled, actix-idempotency, http-status, flex, actix-client, actx-web, actx, http-fields, http-lite, qpack, actix-websockets, actix-websocket, actix-proxy-protocol, actix-client-ip, http-field, http-version, http-status-code, proxyproto, httpea, http-accept, http-method, actix-lab, actix-signature, actix-crypto, trix, actix-extras, actix-extra, tix, actix-web-test, another, robjtede

  • Crate contains junk files

    The crate contains boilerplate Rust files with no real functionality.

• khaled

  • No readme property

    Specify path to a README file for the project, so that information about is included in the crates.io tarball.

• another

  • Could not fetch repository

    We've had trouble cloning git repo from https://gitee\.com/himoney/aj

    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.

  • No readme property

    Specify path to a README file for the project, so that information about is included in the crates.io tarball.

• cwt

  • Internal error

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

• cborwebtoken

  • Internal error

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

• accent

  • Internal error

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

• accent-net

  • Internal error

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

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