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.

• secubot

  • Latest stable release is old

    It's been over 2 years. How did the experiment go? 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

  • Dependency itertools 0.12.0 is significantly outdated

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

    In Cargo, different 0.x versions are considered incompatible, so this is a semver-major upgrade.

    itertools versions

  • Dependency octocrab 0.33 is significantly outdated

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

    octocrab versions

  • Dependency config 0.13 is outdated

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

    config versions

  • Dependency poise 0.5 is outdated

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

    poise versions

  • Imprecise dependency requirement tokio = 1

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

• cot

  • Dependency schemars 0.9 is significantly outdated

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

    schemars versions

  • Dependency time 0.3.46 is significantly outdated

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

    time versions

  • Dependency askama 0.15.4 is outdated

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

    askama versions

  • Dependency chumsky 0.9.3 is outdated

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

    chumsky versions

  • Dependency fake 4 is outdated

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

    fake versions

  • Dependency tower-livereload 0.9.6 is outdated

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

    tower-livereload versions

  • Imprecise dependency requirement derive_more = 2

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

    derive_more versions

• cot_codegen

  • Imprecise dependency requirement syn = 2

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

    syn versions

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["cot", "web-framework", "orm", "lazy-evaluation", "framework-for-lazy"] (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.

• cot-cli

  • Dependency clap_mangen 0.2.31 is a bit outdated

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

    clap_mangen versions

  • Imprecise dependency requirement clap_complete = 4

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

    clap_complete versions

• cot_core

  • Dependency schemars 0.9 is significantly outdated

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

    schemars versions

  • Dependency askama 0.15.4 is outdated

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

    askama versions

  • Imprecise dependency requirement derive_more = 2

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

    derive_more versions

• cot_macros

  • Dependency askama_derive 0.15.3 is significantly outdated

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

    askama_derive versions

  • Imprecise dependency requirement proc-macro-crate = 3

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

    proc-macro-crate versions

• rurs

  • Crate contains junk files

    The crate contains boilerplate Rust files with no real functionality.

  • No readme property

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

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