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.

• async-graphql-extension-apollo-tracing

  • Dependency async-std 1 has issues

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

    async-std crate

  • Dependency derive_builder 0.13 is significantly outdated

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

    derive_builder versions

  • Dependency tonic-build 0.10 is significantly outdated

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

    tonic-build versions

  • Dependency prost-build 0.12.3 is outdated

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

    prost-build versions

  • Dependency protox 0.6.0 is outdated

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

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

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

    Crate features

• async-graphql-extension-apollo-tracing, swarmd, wasmio, roster, swarmd_instruments

  • Imprecise dependency requirement anyhow = 1

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

    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.

    anyhow versions

• octokit-rs

  • Dependency typify =0.0.15 is significantly outdated

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

    typify versions

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

    serde versions

  • Imprecise dependency requirement syn = 2

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

  • Locked dependency version typify =0.0.15

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    typify versions

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["database"] 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

• json-predicate

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

    serde versions

  • Dependency chrono-tz 0.8 is outdated

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

    chrono-tz versions

  • Dependency langtag 0.3 is outdated

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

    langtag versions

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["text-processing", "filesystem"] to the Cargo.toml.

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["predicate", "json-predicate", "abc", "string", "draft-snell-json-07"] (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.

• swarmd_generated

  • Failed to verify create's content against its repository

    Could not check any 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-24

    This check is experimental.

    Forum thread

  • 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

  • Dependency serde_with ^2.0 is outdated

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

    serde_with versions

  • Latest prerelease is old

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

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["generated", "swarmd-generated", "organization", "model", "blblbllb"] (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.

  • 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

• sharded-thread

  • Missing categories

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

    List of available categories

  • Imprecise dependency requirement non_blocking_mutex = 3

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

    non_blocking_mutex versions

• roster

  • Latest stable release is old

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

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

    Maintenance status field docs

  • Published crate doesn't match its repository

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

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

    • Cargo.lock exists, but elsewhere in the repo.

    Looked for the crate in app/roster/. Fetched https://github.com/miaxos/roster.git tagged v0.1.4 (19b6409d2837707a906763896dfe46095a0302ca).

    Checked on 2024-07-28

    Forum thread

  • Dependency atoi_simd 0.15 is outdated

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

    atoi_simd versions

  • Dependency config 0.14 is outdated

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

    config versions

  • Dependency rand 0.8 is a bit outdated

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

    rand versions

  • Dependency rustc-hash 1.1.0 is a bit outdated

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

    rustc-hash versions

  • Missing categories

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

    List of available categories

• shipliftexp

  • Dependency base64 0.10 is significantly outdated

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

    base64 versions

  • Dependency bytes 0.4 is significantly outdated

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

    bytes versions

  • Dependency futures 0.1 has issues

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

    futures crate

  • Dependency http 0.1 is significantly outdated

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

    http versions

  • Dependency hyper 0.12 is significantly outdated

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

    hyper versions

  • Dependency hyper-openssl 0.7 is significantly outdated

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

    hyper-openssl versions

  • Dependency hyperlocal 0.6 is significantly outdated

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

    hyperlocal versions

  • Dependency tokio 0.1 has issues

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

    tokio crate

  • Dependency tokio-codec 0.1 has issues

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

    tokio-codec crate

  • Dependency tokio-io 0.1 has issues

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

    tokio-io crate

  • Dependency url 1.7 is significantly outdated

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

    url versions

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

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

    Maintenance status field docs

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

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

    List of available categories

• wasmio

  • Dependency parking_lot =0.12.1 is significantly outdated

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

    parking_lot versions

  • Dependency quick-xml 0.31 is significantly outdated

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

    quick-xml versions

  • Dependency tokio =1.35 is significantly outdated

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

    tokio versions

  • Locked dependency version axum =0.7

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    axum versions

  • Locked dependency version hyper =0.14

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    hyper versions

  • Locked dependency version parking_lot =0.12.1

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    parking_lot versions

  • Locked dependency version tokio =1.35

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    tokio versions

  • Dependency axum =0.7 is outdated

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

    axum versions

  • Dependency axum-extra 0.9 is outdated

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

    axum-extra versions

  • Dependency axum-serde 0.2 is outdated

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

    axum-serde versions

  • Dependency config 0.14 is outdated

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

    config versions

  • Dependency hyper =0.14 is outdated

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

    hyper versions

  • Dependency strum 0.26 is outdated

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

    strum versions

  • Dependency tower 0.4 is outdated

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

    tower versions

  • Dependency tower-http 0.5 is outdated

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

    tower-http versions

• wasmio-aws-types

  • Dependency derive_builder 0.13 is significantly outdated

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

    derive_builder versions

  • Dependency tokio =1.35 is significantly outdated

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

    tokio versions

  • Locked dependency version axum =0.7

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    axum versions

  • Locked dependency version tokio =1.35

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    tokio versions

  • Dependency axum =0.7 is outdated

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

    axum versions

  • Imprecise dependency requirement derivative = 2

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

    derivative versions

  • Missing categories

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

    List of available categories

  • Missing keywords

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

• swarmd

  • Failed to verify create's content against its repository

    Could not check any 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-24

    Forum thread

  • Dependency deno_core 0.232 is significantly outdated

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

    deno_core versions

  • Dependency axum 0.6.12 is outdated

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

    axum versions

  • Dependency base64 0.21 is outdated

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

    base64 versions

  • Dependency config 0.13 is outdated

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

    config versions

  • Dependency derive_builder 0.12 is outdated

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

    derive_builder versions

  • Dependency directories 5 is outdated

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

    directories versions

  • Dependency git2 0.18 is outdated

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

    git2 versions

  • Dependency notify 6 is outdated

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

    notify versions

  • Dependency notify-debouncer-full 0.3 is outdated

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

    notify-debouncer-full versions

  • Dependency reqwest 0.11 is outdated

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

    reqwest versions

  • Dependency self_update 0.39 is outdated

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

    self_update versions

  • Dependency tower-http 0.4 is outdated

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

    tower-http versions

  • Dependency webbrowser 0.8.8 is outdated

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

    webbrowser versions

• swarmd_instruments

  • Failed to verify create's content against its repository

    Could not check any 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

  • Missing categories

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

    List of available categories

  • Could not fetch repository

    We've had trouble cloning git repo from https://github\.com/swarmd\_io/swarmd\.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 sentry 0.32 is significantly outdated

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

    sentry versions

  • Dependency sentry-tracing 0.32 is outdated

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

    sentry-tracing versions

  • Missing keywords

    Help users find your crates. Add keywords = ["instrumentation", "swarmd-instruments", "instrument"] (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.

• swarmd_slug-rs

  • Failed to verify create's content against its repository

    Could not check any 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

  • Could not fetch repository

    We've had trouble cloning git repo from https://github\.com/swarmd\_io/swarmd\.git

  • Imprecise dependency requirement thiserror = 1

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

  • Latest prerelease is old

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

  • Missing categories

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

    List of available categories

  • Missing keywords

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

• asbru

  • Dependency async-graphql-parser 2.9.10 is significantly outdated

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

    async-graphql-parser versions

  • Dependency async-graphql-value 2.9.10 is significantly outdated

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

    async-graphql-value versions

  • Dependency convert_case 0.4.0 is significantly outdated

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

    convert_case 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

  • Dependency clap 2.33.0 is outdated

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

    clap versions

  • Dependency codegen 0.1.3 is outdated

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

    codegen versions

  • Dependency http 0.2.4 is outdated

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

    http versions

  • Dependency thiserror 1.0.26 is a bit outdated

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

    thiserror versions

  • Dependency toml 0.5 is outdated

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

    toml versions

  • Imprecise dependency requirement regex = 1

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

    regex versions

• github-control

  • Dependency clap 3.0.0-beta.1 is significantly outdated

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

    clap versions

  • Dependency reqwest 0.10.7 is significantly outdated

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

    reqwest versions

  • Dependency webbrowser 0.5.5 is significantly outdated

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

    webbrowser versions

  • Dependency confy 0.4.0 is outdated

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

    confy versions

  • Dependency graphql_client 0.9.0 is outdated

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

    graphql_client versions

  • Dependency termion 1.5.5 is outdated

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

    termion 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

• opentelemetry-datadog-cloudflare

  • Dependency opentelemetry-http 0.6 is significantly outdated

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

    opentelemetry-http versions

  • Dependency tonic-build 0.8 is significantly outdated

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

    tonic-build versions

  • 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 opentelemetry-semantic-conventions 0.9 is outdated

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

    opentelemetry-semantic-conventions versions

  • Dependency prost 0.11 is outdated

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

    prost versions

  • Dependency prost-build 0.11 is outdated

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

    prost-build 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

  • Dependency thiserror 1.0 is a bit outdated

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

    thiserror versions

  • Imprecise dependency requirement lazy_static = 1

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

    lazy_static versions

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

    Crate features

• json-predicate, swarmd, sharded-thread, wasmio, roster, swarmd_slug-rs

  • Dependency thiserror 1 is a bit outdated

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

    thiserror versions

• swarmd_local_runtime

  • Dependency deno_core 0.232 is significantly outdated

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

    deno_core versions

  • Dependency deno_crypto 0.140 is significantly outdated

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

    deno_crypto versions

  • Dependency deno_tls 0.113 is significantly outdated

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

    deno_tls 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 deno_ast 0.31 is outdated

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

    deno_ast versions

  • Dependency deno_console 0.126 is outdated

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

    deno_console versions

  • Dependency deno_fetch 0.150 is significantly outdated

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

    deno_fetch versions

  • Dependency deno_http 0.123 is outdated

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

    deno_http versions

  • Dependency deno_net 0.118 is significantly outdated

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

    deno_net versions

  • Dependency deno_url 0.126 is outdated

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

    deno_url versions

  • Dependency deno_web 0.157 is significantly outdated

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

    deno_web versions

  • Dependency deno_webidl 0.126 is outdated

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

    deno_webidl versions

  • Dependency deno_websocket 0.131 is significantly outdated

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

    deno_websocket 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

  • Imprecise dependency requirement tokio = 1

    Cargo does not always pick latest versions of dependencies! Specify the version as tokio = "1.45.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 = ["web-programming::http-server"] to the Cargo.toml.

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["deno", "swarmd", "run-time", "worker"] (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.

• wasmio-aws-types, swarmd_slug-rs, swarmd_instruments

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

• asbru, fp-rs, fp-ts

  • 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

• apollo-tracing-protobuf

  • Dependency protobuf 2.18.0 is outdated

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

    protobuf 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

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