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.

• activate

  • Imprecise dependency requirement clap = 4

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

    clap versions

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["config"] 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 = ["env-vars", "configuration", "environment", "settings", "monorepo"] (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.

• error_set

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

    Crate features

• stamp-cli

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

  • Dependency serde_yaml ^0.9 has issues

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

    serde_yaml crate

  • Imprecise dependency requirement anyhow = ^1

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

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["template", "render-template", "stamp", "tool", "command-line-tool"] (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.

• containeryard

  • Dependency jsonschema 0.26 is significantly outdated

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

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

    jsonschema versions

  • Dependency serde_yaml 0.9 has issues

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

    serde_yaml crate

  • Imprecise dependency requirement anyhow = 1

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

  • Published crate doesn't match its repository

    Verified 49 out of 50 files (includes 3 Cargo-generated).

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

    • x.md not found.
    • Cargo.lock not found.

    Fetched https://github.com/mcmah309/containeryard.git 8fa0b67a0e4ae279601f78871866747fb6012d8c.

    Checked on 2024-12-15

    This check is experimental.

    Forum thread

  • Dependency dirs 5 is outdated

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

    Easy way to bump dependencies: cargo install cargo-edit; cargo upgrade -i; Also check out Dependabot service on GitHub.

    dirs 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 = ["container", "yaml-config", "module", "reproducible", "declarative"] (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.

• llmtoolbox

  • README missing from the repository

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

  • Imprecise dependency requirement serde_json = 1

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

  • No readme property

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

  • 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 = ["turning", "functions", "callable", "llms", "api"] (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.

• llama_link

  • Missing categories

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

    List of available categories

  • Published crate doesn't match its repository

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

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

    • x.md not found.
    • Cargo.lock does not match the repository.

    Fetched https://github.com/mcmah309/llama_link.git dc5b62a8c319f064cdc7677eee4ff48bb6a690a8.

    Checked on 2025-01-12

    Forum thread

  • Imprecise dependency requirement bon = 3

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

    bon versions

  • Missing keywords

    Help users find your crates. Add keywords = ["llama", "cpp", "interface", "link", "server"] (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.

• err_trail

  • 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

  • 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 = ["error-logging", "err", "context", "error-context", "tracing"] (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.

• indices

  • 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 = ["interior-mutability", "slice", "mutable", "zero-allocation", "refcell"] (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.

• declare_impl

  • Failed to verify create's content against its repository

    Verified 4 out of 10 files (includes 3 Cargo-generated).

    • warning: The crates.io package has no information about its path inside its repository.
    • warning: Could not find Cargo.toml for this package in its repo (via tags).
      • Make sure the repository URL in Cargo.toml is correct
    • warning: Could not discover crate's location in its repository (via tags).

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

    • Cargo.toml.orig does not match the repository.
    • Cargo.lock not found.
    • src/
      • validate.rs exists, but elsewhere in the repo.
      • expand.rs exists, but elsewhere in the repo.
      • ast.rs exists, but elsewhere in the repo.
      • resolve.rs exists, but elsewhere in the repo.
      • lib.rs does not match the repository.

    Fetched https://github.com/mcmah309/error_set.git 79a103a3289e58c6348e3ec6946e31921cbef6da.

    Checked on 2024-12-15

    Forum thread

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

    syn versions

• to_that

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["conversion", "chaining", "safe", "declarative", "compile"] (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.

• tpp

  • Dependency serde_yaml 0.9 has issues

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

    serde_yaml crate

  • Missing keywords

    Help users find your crates. Add keywords = ["preprocessor", "tera", "command-line", "dockerfile", "templating"] (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.

• vec_to_array

  • 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 = ["stack-allocated", "array-vec", "heap-allocated", "vec-t", "size"] (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.

• surrealdb_migration_engine

  • Dependency error_set 0.6 is outdated

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

    error_set 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 = ["database-migrations", "database-schema", "surrealdb", "migration", "engine"] (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.

• mdbook-tools

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["mdbook", "documentation", "directory", "generate-documentation", "directory-structure"] (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.

• olinker

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["natively", "ollama", "linker", "links", "calling"] (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.

• named_args

  • Missing categories

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

    List of available categories

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

  • Missing keywords

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

• surrealdb_migration_engine, llmtool, error_set_impl

  • 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

• declare_impl, llmtool, error_set_impl, named_args

  • No readme property

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

• llmtool

  • README missing from the repository

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

• declare

  • Dependency error_set_impl =0.8.2 is outdated

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

    error_set_impl versions

  • Failed to verify create's content against its repository

    Verified 25 out of 26 files (includes 3 Cargo-generated).

    • warning: Could not find Cargo.toml for this package in its repo (via vcs info).
      • Make sure the repository URL in Cargo.toml is correct
    • warning: Could not find Cargo.toml for this package in its repo (via tags).
    • warning: Could not discover crate's location in its repository (via tags).
    • warning: Repository fetch error: Broken repo: protocol error, missing OIDs or HEAD.

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

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

    Fetched https://github.com/mcmah309/error_set.git 79a103a3289e58c6348e3ec6946e31921cbef6da.

    Checked on 2024-12-08

    Forum thread

• tracing_utils

  • Crate contains junk files

    The crate contains boilerplate Rust files with no real functionality.

  • README missing from the repository

    We've searched https://github\.com/mcmah309/tracing\_utils\.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.

• set_of

  • Crate is 'reserved'

    Please be respectful of crates.io and don't squat crate names.

    It's OK if you intend to publish this project in the near future. Keep in mind that even if you have good intentions, things may not go as planned. crates.io won't reclaim abandoned crates, so reserving good names may end up wasting the good names.

No issues found in: eros tera-macro

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