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.

• argcall

  • Imprecise dependency requirement thiserror = 2

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

  • Missing keywords

    Help users find your crates. Add keywords = ["enums-variant", "struct-fields", "enum-variants", "callable", "enums-and-structs"] (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.

• untest, ts_init, kumosh-core

  • No readme property

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

• argcall, winnow-regex, greedy_enum

  • Missing categories

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

• untest

  • Missing keywords

    Help users find your crates. Add keywords = ["harness", "binary", "applications"] (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.

• untest, until_needle, phargs-cli, followfile, kumosh-core, phargs, xcolabel, hosts_to

  • Missing categories

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

    List of available categories

• followfile

  • Failed to verify create's content against its repository

    Verified 6 out of 8 files (includes 3 Cargo-generated).

    • warning: Crate tarball has been published from the commit 316d53f9db27f1a5c629f3c9d6f9966adc336cd9, which is not in the repository.
      • Create git tags after comitting any changes, and commit changes after bumping versions and running cargo update.
    • warning: Found a Cargo.toml for this package in its repo (via tags), but the version was different.
      • Make sure to commit and tag after bumping the version number.
    • warning: Had to perform fuzzy search of the head branch due to lack of commit information in the package.

    Files in the crates.io crate compared to the repository:

    • Cargo.lock does not match the repository.
    • Cargo.toml.orig does not match the repository.
    • lib.rs does not match the repository.

    Fetched https://github.com/yamaura/followfile.git c15feb6daa0b4d274a87f32a6ef8dfbdb0c2faee.

    Checked on 2024-10-04

    This check is experimental.

    Forum thread

  • Missing keywords

    Help users find your crates. Add keywords = ["file-reader", "follow", "tail", "tokio", "back-end"] (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 'tokio' 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 'tokio' may have been unintentional.

    Crate features

• phargs

  • Failed to verify create's content against its repository

    Verified 2 out of 4 files (includes 1 Cargo-generated).

    • warning: Crate tarball has been published from the commit 712c55b4e25d7381056faa686b1a18b6f471b788, which is not in the repository.
      • Create git tags after comitting any changes, and commit changes after bumping versions and running cargo update.
    • warning: Found a Cargo.toml for this package in its repo (via tags), but the version was different.
      • Make sure to commit and tag after bumping the version number.
    • warning: Had to perform fuzzy search of the head branch due to lack of commit information in the package.
    • error: Manifest properties don't match: package.version.

    Files in the crates.io crate compared to the repository:

    • lib.rs does not match the repository.

    Looked for the crate in crates/phargs/. Fetched https://github.com/yamaura/phargs.git b192da96213a431ffb1353a47ac1672cd5af78f0.

    Checked on 2024-08-04

    Forum thread

  • Missing keywords

    Help users find your crates. Add keywords = ["command-runner", "sequence-processing", "comma-separated", "bash", "txt"] (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.

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

• kumosh-core

  • README missing from the repository

    We've searched https://github\.com/yamaura/kumosh\.git and could not find a README file there.

  • Missing keywords

    Help users find your crates. Add keywords = ["shell", "cluster"] (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.

• phargs-cli

  • Failed to verify create's content against its repository

    Verified 4 out of 6 files (includes 2 Cargo-generated).

    • warning: Crate tarball has been published from the commit 712c55b4e25d7381056faa686b1a18b6f471b788, which is not in the repository.
      • Create git tags after comitting any changes, and commit changes after bumping versions and running cargo update.
    • warning: Found a Cargo.toml for this package in its repo (via tags), but the version was different.
      • Make sure to commit and tag after bumping the version number.
    • warning: Had to perform fuzzy search of the head branch due to lack of commit information in the package.
    • error: Manifest properties don't match: package.version.

    Files in the crates.io crate compared to the repository:

    • Cargo.lock not found.
    • Cargo.toml.orig does not match the repository.

    Looked for the crate in crates/phargs-cli/. Fetched https://github.com/yamaura/phargs.git b192da96213a431ffb1353a47ac1672cd5af78f0.

    Checked on 2024-07-28

    Forum thread

• greedy_enum

  • README missing from the repository

    We've searched https://github\.com/yamaura/greedy\_enum\.git and could not find a README file there.

  • Imprecise dependency requirement thiserror = 1

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

    thiserror versions

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

  • Missing keywords

    Help users find your crates. Add keywords = ["enums", "greedy", "from-str", "macro"] (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.

• escnul

  • Imprecise dependency requirement thiserror = 2

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

    thiserror versions

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["byte-escaping", "embedding", "shell", "engine", "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.

• anyseq

  • Dependency winnow 0.6.8 is significantly outdated

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

    winnow versions

  • 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

  • Failed to verify create's content against its repository

    Verified 9 out of 10 files (includes 2 Cargo-generated).

    • warning: Crate tarball has been published from the commit 5f5d27ae334b79a9c1da93f43c71c87a2a593394, which is not in the repository.
      • Create git tags after comitting any changes, and commit changes after bumping versions and running cargo update.
    • warning: Found a Cargo.toml for this package in its repo (via tags), but the version was different.
      • Make sure to commit and tag after bumping the version number.
    • warning: Had to perform fuzzy search of the head branch due to lack of commit information in the package.

    Files in the crates.io crate compared to the repository:

    • Cargo.toml.orig does not match the repository.

    Fetched https://github.com/yamaura/anyseq.git 83a36c1cd89fae8ca4610c5cbe40b254dd7c3184.

    Checked on 2024-07-28

    Forum thread

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["lexer", "deserialize", "automatic", "deserializer", "generate"] (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.

• clwrap

  • Dependency futures-lite 1.12.0 is significantly outdated

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

    futures-lite versions

  • Dependency typed-builder 0.11.0 is significantly outdated

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

    typed-builder versions

  • Dependency expectrl 0.6.0 is outdated

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

    expectrl versions

  • Dependency thiserror 1 is outdated

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

    thiserror versions

  • Imprecise dependency requirement regex = 1

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

    regex versions

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

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

    Maintenance status field docs

  • Missing keywords

    Help users find your crates. Add keywords = ["command-line", "run-command", "autologin", "open-terminal", "telnet"] (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 'anyhow' 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 'anyhow', 'clap', 'tracing-subscriber' may have been unintentional.

    Crate features

• ts_init

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["logging", "journald", "stderr", "template", "file-path"] (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.

• winnow-regex

  • Imprecise dependency requirement regex = 1

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

    Help users find your crates. Add keywords = ["regex", "winnow", "parser", "backed", "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.

• until_needle

  • Imprecise dependency requirement regex = 1

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

    Help users find your crates. Add keywords = ["bufread", "needle", "stream-reader", "extension", "search-pattern"] (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.

• entroll-core

  • README missing from the repository

    We've searched https://github\.com/yamaura/entroll\.git and could not find a README file there.

  • Imprecise dependency requirement thiserror = 1

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

    thiserror versions

  • Dependency rand 0.8.5 is outdated

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

    rand versions

  • Dependency thiserror 1 is outdated

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

    thiserror versions

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["random", "bit", "print", "password", "entropy"] (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.

• hosts_to

  • Imprecise dependency requirement thiserror = 1

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

    thiserror versions

• nodeagg

  • Dependency itertools 0.10.3 is outdated

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

    itertools versions

  • 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

• xcolabel

  • Missing keywords

    Help users find your crates. Add keywords = ["convert", "column", "numbers", "label", "0-based"] (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.

• untest_macro, entroll-core, argcall_derive

  • No readme property

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

• untest_macro, ts_init_macros, argcall_derive, regex_with_derive, greedy_enum_derive

  • Imprecise dependency requirement syn = 2

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

• hosts_to, anyseq, greedy_enum

  • Dependency thiserror 1 is outdated

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

    thiserror versions

• rpmvercmp

  • Dependency libloading 0.7.4 is significantly outdated

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

    libloading versions

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

    Crate features

• greedy_enum_derive

  • README missing from the repository

    We've searched https://github\.com/yamaura/greedy\_enum\.git and could not find a README file there.

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

• regex_with_derive

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

• dssh

  • Internal error

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

• entroll

  • Internal error

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

• entroll-dictionaries

  • Internal error

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

• wasui-memory

  • Internal error

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

• sshrpc

  • Internal error

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

• russh-process

  • Internal error

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

• regex_with

  • Internal error

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

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