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.

• ohkami

  • Dependency async-std 1 has issues

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

    async-std crate

  • 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

• exp-cfg-test

  • Published crate doesn't match its repository

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

    Fetched https://github.com/kanarus/exp-cfg-test.git 3c5e07ac660f414412045ade79cdf05cbd1b8817.

    Checked on 2024-12-01

    This check is experimental.

    Forum thread

  • README missing from the repository

    We've searched https://github\.com/kanarus/exp\-cfg\-test\.git and could not find a README file there.

  • No readme property

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

  • Missing categories

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

    Even if there are no categories that fit precisely, pick one that is least bad. You can also propose new categories in crates.io issue tracker.

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["testing", "cfg", "exp-cfg-test", "test", "right"] (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.

• qjack

  • Latest stable release is old

    It's been over 23 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 17 files (includes 2 Cargo-generated).

    Fetched https://github.com/kana-rus/qjack.git 7df24d8272eb9155e2e72ff4f513ab3ffd0ceb7f.

    Checked on 2024-08-10

    Forum thread

  • 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 sqlx 0.6 is outdated

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

    sqlx versions

• serdev

  • 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

  • Locked dependency version serdev_derive =0.2.0

    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.

    serdev_derive versions

• sqlx-d1-core

  • Dependency sqlx-core =0.8.3 is significantly outdated

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

    sqlx-core versions

  • Dependency sqlx-sqlite =0.8.3 is significantly outdated

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

    sqlx-sqlite versions

  • Locked dependency version sqlx-core =0.8.3

    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.

    sqlx-core versions

  • Locked dependency version sqlx-sqlite =0.8.3

    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.

    sqlx-sqlite versions

  • Imprecise dependency requirement rust_decimal = 1

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

    rust_decimal versions

• mews

  • Dependency async-std 1 has issues

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

    async-std crate

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

    async-std versions

• atruct, kozo, litenum, qjack_macros

  • Dependency syn 1.0 is significantly outdated

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

    syn versions

• atruct

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

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

    Maintenance status field docs

• kozo

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

    Maintenance status field docs

• sqlx-d1-macros

  • Dependency sqlx-core =0.8.3 is significantly outdated

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

    sqlx-core versions

  • Dependency sqlx-macros-core =0.8.3 is significantly outdated

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

    sqlx-macros-core versions

• qjack_macros

  • 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

  • Dependency heck 0.4 is outdated

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

    heck versions

• serdev_derive

  • 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-09-15

    Forum thread

No issues found in: uibeam uibeam_macros uibeam_html cargo-metask sqlx-d1 ohkami_lib ohkami_macros ohkami_openapi worker-bindings unsaferef byte_reader aoi aoi_macros

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