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.

• shellfirm

  • Dependency serde_yaml 0.9 has issues

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

    serde_yaml crate

  • Dependency windows-sys 0.59 is significantly outdated

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

    windows-sys versions

  • 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

  • Published crate doesn't match its repository

    Partially verified 115 files (includes 3 Cargo-generated).

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

    • Cargo.lock exists, but elsewhere in the repo.

    Looked for the crate in shellfirm/. Fetched https://github.com/kaplanelad/shellfirm.git tagged v0.3.9 (f2e29bdf27ce4ff0a818df764b3684a93d7299fd).

    Checked on 2026-03-29

    This check is experimental.

    Forum thread

  • Dependency reqwest 0.12 is outdated

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

    reqwest versions

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["development-tools", "command-line-interface"] 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 = ["artificial-intelligence", "prompt", "captcha", "ai-agents", "intercept"] (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 'reqwest' 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 'reqwest', 'portable-pty', 'clap_complete_nushell', 'tokio', 'clap_complete', 'rustix', 'clap', 'windows-sys' may have been unintentional.

    Crate features

• tree-fs

  • Dependency serde_yaml 0.9.27 has issues

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

    serde_yaml crate

  • Dependency rand 0.9.1 is outdated

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

    rand versions

  • Missing categories

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

    List of available categories

• english-to-cron

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["cron-expression", "cron-job", "convert", "nlp", "range"] (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.

• snipgrep

  • Published crate doesn't match its repository

    Could not check any files

    • error: Repository doesn't exist: Can't checkout the repository. It's either gone or private: remote authentication required but no callback set; class=Http (34); code=Auth (-16).
      • Make sure the repository URL in Cargo.toml is correct and works with git clone. The repository must be public.

    Checked on 2024-08-04

    Forum thread

  • Dependency console 0.15.8 is outdated

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

    console versions

  • Dependency scraper 0.19.0 is significantly outdated

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

    scraper versions

  • Dependency thiserror 1.0.61 is outdated

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

    thiserror versions

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["documentation-generator", "snippets", "config", "cli", "demonstrate"] (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.

• snipdoc

  • Dependency console 0.15.8 is outdated

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

    console versions

  • Dependency requestty 0.5.0 is outdated

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

    requestty versions

  • Dependency scraper 0.19.0 is significantly outdated

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

    scraper versions

  • Dependency thiserror 1.0.61 is outdated

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

    thiserror versions

  • Failed to verify create's content against its repository

    Partially verified 95 files (includes 3 Cargo-generated).

    • warning: The crates.io package has no information about its path inside its repository.

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

    • Cargo.lock exists, but elsewhere in the repo.

    Looked for the crate in snipdoc/. Fetched https://github.com/kaplanelad/snipdoc.git tagged v0.1.12 (21849a553bd7436005cb91b2976b3f1a775bf349).

    Checked on 2025-04-30

    Forum thread

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["snippets", "documentation", "inject", "collect", "yaml"] (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.

• github-scopes-rs

  • Missing categories

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

    List of available categories

  • Dependency env_logger 0.8.4 is significantly outdated

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

    env_logger versions

  • Dependency reqwest 0.11.10 is outdated

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

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

    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

• rdocs

  • Dependency serde_yaml 0.9.32 has issues

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

    serde_yaml crate

  • Dependency thiserror 1.0.57 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 = ["development-tools"] to the Cargo.toml.

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["documentation-generator", "codebase", "different", "config", "extract"] (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.

• snipdoc, snipgrep, crazy-train

  • Dependency serde_yaml 0.9.33 has issues

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

    serde_yaml crate

• snipdoc, rdocs, snipgrep

  • Dependency tabled 0.15.0 is significantly outdated

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

    tabled versions

• deep-unpack

  • Dependency derive_builder 0.11.2 is significantly outdated

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

    derive_builder versions

  • Dependency serde_yaml 0.9 has issues

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

    serde_yaml crate

  • Dependency zip 0.6.3 is outdated

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

    zip 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 categories

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

    List of available categories

  • Published crate contains binary files

    The crate contains binary files (JAR file). 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

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

• webql

  • Dependency serde_yaml 0.9.13 has issues

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

    serde_yaml crate

  • Dependency jql 5.1.1 is a bit outdated

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

    jql versions

  • Dependency reqwest 0.11.12 is outdated

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

    reqwest versions

  • Missing categories

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

    List of available categories

• redact-engine, webql, crazy-train

  • 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

• upversion

  • Imprecise dependency requirement anyhow = 1

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

    anyhow versions

  • Dependency env_logger 0.9.0 is significantly outdated

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

    env_logger versions

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["client", "latest", "newer-version", "link", "released"] (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.

• crazy-train

  • Dependency colored 2.1.0 is outdated

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

    colored versions

  • Dependency duct_sh 0.13.7 is outdated

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

    duct_sh versions

  • Dependency rand 0.8 is outdated

    Consider upgrading to 0.10.1 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 = ["development-tools::testing"] to the Cargo.toml.

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["fuzzing", "command-line-interface", "testing", "execution", "randomized"] (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.

• active-storage

  • Dependency thiserror 1.0.56 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 = ["web-programming", "filesystem"] to the Cargo.toml.

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["cloud-storage", "active", "uploading", "facilitate", "mirroring"] (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.

• redact-engine

  • Missing categories

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

    List of available categories

• redact-engine, mask-text, webql, upversion

  • 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

• redact-engine, mask-text, webql

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

• mask-text

  • Missing categories

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

    List of available categories

• rustyrails

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

• loco

  • Internal error

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

• loco-rs

  • Internal error

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

• loco-gen

  • Internal error

    We couldn't check this crate at this time, because: timed out validating Origin( lib.rs/crates/loco-gen ). Please try again later.

• loco-openapi

  • Internal error

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

• keyscope

  • Internal error

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

• rrgen

  • Internal error

    We couldn't check this crate at this time, because: timed out validating Origin( lib.rs/crates/rrgen ). Please try again later.

• loco-cli

  • Internal error

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

• service_policy_kit

  • Internal error

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

• loco-extras

  • Internal error

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

• rustyrails-cli

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/rustyrails-cli ) 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.