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.

• scyllax

  • Dependency getrandom 0.2 is outdated

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

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

    getrandom versions

  • Dependency prost-types 0.12 is outdated

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

    prost-types versions

  • Dependency scylla 0.12 is outdated

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

    scylla versions

  • Failed to verify create's content against its repository

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

    • warning: Crate tarball has been published from the commit fcfc4a97727fa0dc7fc820bee82afd195e1669eb, 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.

    Looked for the crate in scyllax/. Fetched https://github.com/trufflehq/scyllax.git b919b7d187b7106ac5555871a8b270463361eb02.

    Checked on 2024-08-04

    This check is experimental.

    Forum thread

  • Imprecise dependency requirement mac_address = 1

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

    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.

    mac_address versions

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["database"] 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 = ["scylla", "query", "sqlx", "orm", "discord"] (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 'prost-types' 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 'prost-types', 'serde', 'serde_json' may have been unintentional.

    Crate features

• github-webhooks

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

  • Latest prerelease is old

    It's been over 19 months. 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

  • Dependency axum 0.6 is outdated

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

    axum versions

  • Dependency headers 0.3.8 is outdated

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

    headers versions

  • Dependency http 0.2.9 is 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.

    http versions

  • Dependency ring 0.16.20 is outdated

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

    ring versions

  • Dependency thiserror 1.0.40 is a bit outdated

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

    thiserror versions

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["github-webhook", "framework", "web-framework", "axum"] (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.

• cf-turnstile

  • Dependency secrecy 0.8.0 is a bit outdated

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

    secrecy versions

  • Imprecise dependency requirement hyper = 1

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

    hyper versions

• scyllax-macros-core

  • Imprecise dependency requirement syn = 2

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

    syn versions

  • Dependency convert_case 0.6.0 is a bit outdated

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

    convert_case versions

  • Failed to verify create's content against its repository

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

    • warning: Crate tarball has been published from the commit fcfc4a97727fa0dc7fc820bee82afd195e1669eb, 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.

    Looked for the crate in scyllax-macros-core/. Fetched https://github.com/trufflehq/scyllax.git 919b0bbd8713bf3220a112cb91421b3ad08b39e0.

    Checked on 2024-07-24

    Forum thread

  • 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 = ["macro", "query", "compile-time", "scyllax", "system"] (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.

• imgdl

  • Dependency indicatif 0.15 is significantly outdated

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

    indicatif versions

  • Dependency reqwest 0.10 is significantly outdated

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

    reqwest versions

  • Dependency tokio 0.2 has issues

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

    tokio crate

  • Dependency clap 2 is outdated

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

    clap versions

  • Dependency env_logger 0.7 is outdated

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

    env_logger versions

  • Dependency toml 0.5 is outdated

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

    toml versions

  • Imprecise dependency requirement clap = 2

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

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

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

    Maintenance status field docs

  • Missing categories

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

    List of available categories

• scyllax-cli

  • Dependency scylla 0.12 is outdated

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

    scylla versions

  • Failed to verify create's content against its repository

    Verified 14 out of 15 files (includes 3 Cargo-generated).

    • warning: Crate tarball has been published from the commit fcfc4a97727fa0dc7fc820bee82afd195e1669eb, 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 not found.
    • Cargo.toml.orig does not match the repository.

    Looked for the crate in scyllax-cli/. Fetched https://github.com/trufflehq/scyllax.git e08edab62b979aee1f0d4af96e31b4cd901e70ea.

    Checked on 2024-07-24

    Forum thread

  • Imprecise dependency requirement clap = 4

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

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["scyllax", "migration", "system", "cli", "scylla"] (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.

• scyllax, cf-turnstile, merriam-webster-http

  • Dependency thiserror 1 is a bit outdated

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

    thiserror versions

• scyllax-parser

  • Dependency nom 7 is a bit outdated

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

    nom versions

  • Failed to verify create's content against its repository

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

    • warning: Crate tarball has been published from the commit fcfc4a97727fa0dc7fc820bee82afd195e1669eb, 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.

    Looked for the crate in scyllax-parser/. Fetched https://github.com/trufflehq/scyllax.git b919b7d187b7106ac5555871a8b270463361eb02.

    Checked on 2024-07-24

    Forum thread

• scyllax-macros

  • 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 fcfc4a97727fa0dc7fc820bee82afd195e1669eb, 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:

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

    Looked for the crate in scyllax-macros/. Fetched https://github.com/trufflehq/scyllax.git fe7b7b64b5b34d9bc4254b91e72706a42ba74888.

    Checked on 2024-07-24

    Forum thread

• merriam-webster-model, merriam-webster-http

  • Imprecise dependency requirement serde = 1

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

• merriam-webster-http

  • Dependency hyper 0.14 is outdated

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

    hyper versions

  • Dependency hyper-rustls 0.24 is outdated

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

    hyper-rustls versions

  • Dependency hyper-tls 0.5 is outdated

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

    hyper-tls versions

  • Dependency secrecy 0.8.0 is a bit outdated

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

    secrecy versions

• wttr, kwp

  • Missing categories

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

    List of available categories

• merriam-webster-transformers

  • Dependency nom 7 is a bit outdated

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

    nom versions

  • Latest prerelease is old

    It's been over 15 months. 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

• wttr

  • Dependency reqwest 0.10 is significantly outdated

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

    reqwest versions

  • Dependency clap 2 is outdated

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

    clap versions

  • Imprecise dependency requirement clap = 2

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

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

    Maintenance status field docs

• wyze

  • Crate contains junk files

    The crate contains boilerplate Rust files with no real functionality.

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

No issues found in: nsfw

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