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.

• lol_html

  • Dependency selectors 0.33 is significantly outdated

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

    selectors versions

• cf-rustracing

  • Dependency rand 0.8.1 is outdated

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

    rand versions

  • Imprecise dependency requirement tokio = 1

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

    tokio versions

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

    Crate features

• shellflip

  • Dependency nix 0.25 is significantly outdated

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

    nix versions

  • Dependency sd-notify 0.3 is significantly outdated

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

    sd-notify versions

  • Imprecise dependency requirement serde = 1

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

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

    thiserror versions

  • Missing categories

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

• cf-reqwest

  • Dependency cookie_store 0.21.0 is significantly outdated

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

    cookie_store versions

  • Dependency h3 0.0.6 is significantly outdated

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

    h3 versions

  • Dependency h3-quinn 0.0.7 is significantly outdated

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

    h3-quinn versions

  • Dependency rustls-native-certs 0.7 is significantly outdated

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

    rustls-native-certs versions

  • Dependency system-configuration 0.6.0 is significantly outdated

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

    system-configuration versions

  • Dependency windows-registry 0.2 is significantly outdated

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

    windows-registry versions

  • Dependency hickory-resolver 0.24 is outdated

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

    hickory-resolver versions

  • Dependency wasm-streams 0.4 is a bit outdated

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

    wasm-streams versions

  • Dependency webpki-roots 0.26.0 is outdated

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

    webpki-roots versions

  • Imprecise dependency requirement http = 1

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

    http versions

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

    Crate features

• cloudflare-soos

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

• svg-hush

  • Dependency xml-rs 0.8.17 has issues

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

    xml-rs crate

• boring-sys

  • Missing keywords

    Help users find your crates. Add keywords = ["boring-ssl", "tls", "built", "https-connector", "bindings"] (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.

• all-the-same

  • Dependency syn 1 is significantly outdated

    Upgrade to 2.0.114 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.114". 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

• foundations-macros

  • Imprecise dependency requirement syn = 2

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

  • Dependency darling 0.21 is outdated

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

    darling versions

• two-rusty-forks-macro

  • Dependency syn 1 is significantly outdated

    Upgrade to 2.0.114 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.114". 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

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

  • 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

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

    Use OR instead of /.

    SPDX license list

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

• httx

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

    This check is experimental.

    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/cloudflare/httx\.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.

  • No readme property

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

  • Missing keywords

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

• quiche-mallard

  • Dependency qlog 0.13 is significantly outdated

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

    qlog versions

  • Dependency sfv 0.9 is significantly outdated

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

    sfv versions

  • Dependency intrusive-collections 0.9.5 is slightly outdated

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

    intrusive-collections 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

  • Optional dependency 'foreign-types-shared' 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 'foreign-types-shared', 'boring', 'pkg-config' may have been unintentional.

    Crate features

  • Using outdated edition for no reason

    We estimate that this crate requires at least Rust 1.66, 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

• hyper-boring

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/hyper-boring ) failed. Please try again later.

• tokio-boring

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/tokio-boring ) failed. Please try again later.

• boring

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/boring ) failed. Please try again later.

• foundations

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/foundations ) failed. Please try again later.

• cf-rustracing-jaeger

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/cf-rustracing-jaeger ) failed. Please try again later.

• two-rusty-forks

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/two-rusty-forks ) failed. Please try again later.

• data-url-encode-macro

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/data-url-encode-macro ) failed. Please try again later.

• data-url-encode-macro-impl

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/data-url-encode-macro-impl ) failed. Please try again later.

No issues found in: cloudflare-zlib-sys cloudflare-zlib

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