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.

• address

  • Missing keywords

    Help users find your crates. Add keywords = ["networking", "processing", "types", "aids", "owned"] (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.

• lex

  • Failed to verify create's content against its repository

    Verified 18 out of 36 files (includes 2 Cargo-generated).

    • warning: Crate tarball has been published from the commit 639f478b076aa89e96b08a299d190e78ac98d927, 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.
    • lib.rs does not match the repository.
    • comment_config.rs does not match the repository.
    • src/context/
      • error.rs does not match the repository.
      • parse_context.rs does not match the repository.
      • match_prefix.rs does not match the repository.
      • mod.rs does not match the repository.
      • exact.rs does not match the repository.
      • split.rs does not match the repository.
      • symbol.rs does not match the repository.
    • src/context/comments/
      • line_comment.rs does not match the repository.
      • white_line_comments.rs does not match the repository.
      • line_comment_block.rs does not match the repository.
    • src/context/whitespace/
      • line_ending.rs does not match the repository.
      • whitespace.rs does not match the repository.
      • rest_of_line.rs does not match the repository.
      • white_lines.rs does not match the repository.
    • token.rs does not match the repository.

    Fetched https://github.com/nikdeapen/lex.git 86e873b70f0f8a828fad926863b21d71d2048991.

    Checked on 2025-01-26

    This check is experimental.

    Forum thread

  • 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 = ["programming-language", "parser", "aids"] (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.

• web-scrape, clerr, synio

  • Missing categories

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

    List of available categories

• web-scrape

  • Dependency address 0.12.0 is outdated

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

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

    address versions

  • Dependency scraper 0.22.0 is outdated

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

    scraper versions

  • Dependency web-url 0.4.0 is slightly outdated

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

    web-url versions

  • Failed to verify create's content against its repository

    Verified 11 out of 14 files (includes 2 Cargo-generated).

    • warning: Crate tarball has been published from the commit 23deb5424a918ff2e1dd4d0d8ba09033f74e43ad, 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.
    • src/scrape/
      • mod.rs does not match the repository.
      • error.rs does not match the repository.

    Fetched https://github.com/nikdeapen/web-scrape.git 7ccf3fa8020a4dd7ccd10c706717af1dc63a6f90.

    Checked on 2025-02-02

    Forum thread

  • Missing keywords

    Help users find your crates. Add keywords = ["scraping", "data", "web", "aids"] (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.

• code-gen

  • Failed to verify create's content against its repository

    Verified 67 out of 69 files (includes 2 Cargo-generated).

    • warning: Crate tarball has been published from the commit aab04da40f05197044befbcbb6f72b7230c81cb2, 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.
    • mod.rs does not match the repository.

    Fetched https://github.com/nikdeapen/code-gen.git 8744ac69a6621f5782c03d41abf92fc6e1bf33cb.

    Checked on 2025-01-26

    Forum thread

  • Missing categories

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

    List of available categories

  • Missing keywords

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

• enc

  • 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 = ["data-encoding", "base64", "data-processing", "encoded", "hex"] (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.

• file-storage

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["storage", "accessing", "aids", "file-like"] (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 'dashmap' 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 'dashmap', 'bytes', 'once_cell', 'tokio', 'aws-config', 'aws-sdk-s3' may have been unintentional.

    Crate features

• address, web-url, inet

  • Missing categories

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

    List of available categories

• web-url

  • Missing keywords

    Help users find your crates. Add keywords = ["url", "processing", "web-based", "aids"] (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.

• custom-string

  • Missing categories

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

    List of available categories

  • Missing keywords

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

• clerr

  • Missing keywords

    Help users find your crates. Add keywords = ["error", "displaying", "command-line", "aids"] (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.

• inet

  • Latest stable release is old

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

• synio

  • Latest stable release is old

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

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