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.

• tailwind_fuse

  • Published crate doesn't match its repository

    Partially verified 20 files (includes 2 Cargo-generated).

    Looked for the crate in fuse/. Fetched https://github.com/gaucho-labs/tailwind-fuse.git 5bed822577cc0448ab006a12d11491168a725a27.

    Checked on 2025-01-26

    This check is experimental.

    Forum thread

  • Dependency nom 7 is a bit outdated

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

    Easy way to bump dependencies: cargo install cargo-edit; cargo upgrade -i; Also check out Dependabot service on GitHub.

    nom versions

  • Missing categories

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

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

    Crate features

• leptos_query_devtools

  • Missing categories

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

    List of available categories

  • Failed to verify create's content against its repository

    Partially verified 17 files (includes 2 Cargo-generated).

    • warning: The crates.io package has no information about its path inside its repository.
    • warning: There is no matching git tag containing version '0.1.3'.
      • git tag v0.1.3 d79d5400dbd5410dd4892e595907a3fcfd534dcc; git push origin --tags

    Looked for the crate in devtools/. Fetched https://github.com/gaucho-labs/leptos-query.git d79d5400dbd5410dd4892e595907a3fcfd534dcc.

    Checked on 2024-08-04

    Forum thread

  • Optional dependency 'wasm-bindgen' 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 'wasm-bindgen', 'js-sys', 'web-sys' may have been unintentional.

    Crate features

• leptos_query

  • Dependency indexed_db_futures 0.4 is outdated

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

    indexed_db_futures versions

  • Failed to verify create's content against its repository

    Partially verified 22 files (includes 2 Cargo-generated).

    • warning: The crates.io package has no information about its path inside its repository.

    Looked for the crate in query/. Fetched https://github.com/gaucho-labs/leptos-query.git d79d5400dbd5410dd4892e595907a3fcfd534dcc.

    Checked on 2024-07-24

    Forum thread

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

    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

  • Missing categories

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

    List of available categories

  • Optional dependency 'web-sys' 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 'web-sys', 'indexed_db_futures', 'tokio', 'js-sys', 'async_cell', 'miniserde', 'gloo-timers' may have been unintentional.

    Crate features

• leptos_query, leptos_query_devtools, leptos_image

  • Dependency leptos 0.6 is outdated

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

    leptos versions

• leptos_image

  • Dependency serde_qs 0.12 is significantly outdated

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

    serde_qs versions

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

    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.

    thiserror 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 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 dashmap 5 is outdated

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

    dashmap versions

  • Dependency image 0.24 is outdated

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

    image versions

  • Dependency leptos_meta 0.6 is outdated

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

    leptos_meta versions

  • Dependency leptos_router 0.6 is outdated

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

    leptos_router versions

  • Dependency thiserror 1 is a bit outdated

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

    thiserror 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.2 to get all the fixes, and avoid causing duplicate dependencies in projects.

    tower-http versions

  • Dependency webp 0.2 is outdated

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

    webp 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

• tailwind_fuse_macro

  • 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

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