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.

• dtoolkit

  • Imprecise dependency requirement indexmap = 2

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

    indexmap versions

• cot_codegen

  • Imprecise dependency requirement syn = 2

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

    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 = ["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.

• m4tx-crate-test

  • Missing categories

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

    List of available categories

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

  • No readme property

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

  • 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

  • Dependency cot 0.3.1 is a bit outdated

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

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

    cot versions

  • Missing keywords

    Help users find your crates. Add keywords = ["testing", "playground", "myself", "meant", "anything"] (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.

• riichi_hand

  • Dependency resvg 0.45.0 is outdated

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

    resvg versions

  • Dependency tiny-skia 0.11.4 is outdated

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

    tiny-skia versions

  • Dependency usvg 0.45.0 is outdated

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

    usvg versions

  • Optional dependency 'resvg' 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 'resvg', 'rayon', 'usvg', 'image', 'tiny-skia' may have been unintentional.

    Crate features

• flareon

  • Missing categories

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

    List of available categories

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

  • Missing keywords

    Help users find your crates. Add keywords = ["web-framework", "modern", "ease", "focused", "speed"] (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 cargo_toml 0.22 is outdated

    Consider upgrading to 1.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.

    cargo_toml versions

  • 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

• ryg-rans-sys

  • Dependency bindgen 0.69.4 is significantly outdated

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

    bindgen 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

• htscodecs-sys

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

    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

  • Published crate contains binary files

    The crate contains binary files (obscure autoconf code). Crates are meant to be compiled from source. Please check that you haven't published temporary build files by accident. If you have test fixtures, consider excluding them from crates-io tarball, since Cargo doesn't run tests from crates-io packages.

    Audit page

• securer-string

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

    serde versions

  • Missing categories

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

    List of available categories

• cot

  • Internal error

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

No issues found in: swagger-ui-redist rans

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