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.

• marigold

  • Dependency convert_case 0.6.0 is a bit outdated

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

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

    convert_case versions

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["compilers"] 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 = ["marigold", "dsl", "filter", "return", "lalrpop"] (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.

  • Optional dependency 'convert_case' 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 'convert_case', 'clap', 'home' may have been unintentional.

    Crate features

• csp-hashes

  • Missing categories

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

    List of available categories

  • Dependency scraper 0.16.0 is significantly outdated

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

    scraper versions

  • Published crate doesn't match its repository

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

    Fetched https://github.com/dominicburkart/csp-hashes.git 04bf88bf79c672b7a888c209e41680434a698585.

    Checked on 2024-07-28

    This check is experimental.

    Forum thread

  • Dependency base64 0.21.2 is outdated

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

    base64 versions

  • Missing keywords

    Help users find your crates. Add keywords = ["csp", "csp-hashes", "hash", "html", "script"] (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.

• turbolift

  • Dependency actix-web 3 is significantly outdated

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

    actix-web versions

  • 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 tokio-compat-02 0.1 is outdated

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

    tokio-compat-02 versions

  • Imprecise dependency requirement actix-web = 3

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

    actix-web versions

• funfun

  • Latest stable release is old

    It's been over 6 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

  • 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

• marigold-impl

  • Dependency async-compression 0.3.14 is significantly outdated

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

    async-compression versions

  • Dependency async-std 1 has issues

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

    async-std crate

  • Locked dependency version gen-nested-iter-yield =0.1.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.

    gen-nested-iter-yield versions

  • Dependency binary-heap-plus 0.4.1 is significantly outdated

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

    binary-heap-plus versions

  • Dependency itertools 0.10.2 is outdated

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

    itertools versions

  • Imprecise dependency requirement flate2 = 1

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

    flate2 versions

• fast_text

  • Latest stable release is old

    It's been over 6 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

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

    More info

  • Missing categories

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

    List of available categories

• turbolift_internals

  • Dependency cached 0.19 is significantly outdated

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

    cached versions

  • Dependency k8s-openapi 0.11.0 is significantly outdated

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

    k8s-openapi versions

  • Dependency kube 0.51.0 is significantly outdated

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

    kube versions

  • Dependency kube-runtime 0.51.0 is significantly outdated

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

    kube-runtime versions

  • Dependency rand 0.7 is significantly outdated

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

    rand versions

  • Dependency syn 1 is significantly outdated

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

    syn versions

  • Dependency uuid 0.8 is significantly outdated

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

    uuid versions

  • Imprecise dependency requirement anyhow = 1

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

    anyhow versions

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

    Detecting docs.rs

  • Dependency reqwest 0.11 is outdated

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

    reqwest versions

  • Dependency tokio-compat-02 0.1 is outdated

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

    tokio-compat-02 versions

  • Dependency toml 0.5 is outdated

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

    toml 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 = ["turbolift", "internal", "turbolift-internals"] (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.

• marigold-grammar

  • Dependency itertools 0.10.2 is outdated

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

    itertools versions

  • Dependency lalrpop 0.19.8 is outdated

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

    lalrpop versions

  • Dependency lalrpop-util 0.19.8 is outdated

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

    lalrpop-util versions

  • Imprecise dependency requirement regex = 1

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

    regex versions

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["marigold", "marigold-grammar", "grammar", "filter", "return"] (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.

• turbolift, turbolift_internals, turbolift_macros

  • Latest stable release is old

    It's been over 3 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

• marigold-grammar, turbolift_internals, marigold-impl, marigold-macros, turbolift_macros

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

• turbolift_macros

  • Dependency cached 0.19 is significantly outdated

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

    cached versions

  • Dependency syn 1 is significantly outdated

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

    syn versions

  • Imprecise dependency requirement fs_extra = 1

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

    fs_extra versions

No issues found in: gen-nested-iter-yield

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