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.

• zsh-git-prompt-rs, lisplings

  • Missing categories

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

• seqlings

  • 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 = ["learning-exercise", "interactive-exercises", "stack-based", "seq", "show"] (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.

• seqlings, lisplings, wscat-rs

  • Imprecise dependency requirement clap = ^4

    Cargo does not always pick latest versions of dependencies! 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

• zimhide

  • Failed to verify create's content against its repository

    Could not check any files

    • warning: The crates.io package has no information about its path inside its repository.
    • 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 2026-02-22

    This check is experimental.

    Forum thread

  • Imprecise dependency requirement anyhow = ^1

    Cargo does not always pick latest versions of dependencies! 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

  • Dependency base64 ^0.22 is a bit outdated

    Consider upgrading to the latest version 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.

    base64 versions

  • Dependency chacha20poly1305 ^0.10 is a bit outdated

    Consider upgrading to the latest version to get all the fixes and improvements.

    chacha20poly1305 versions

  • Dependency ed25519-dalek ^2 is a bit outdated

    Consider upgrading to the latest version to get all the fixes and improvements.

    ed25519-dalek versions

  • Dependency rand ^0.8 is outdated

    Consider upgrading to the latest version to get all the fixes and improvements.

    rand versions

  • Dependency thiserror ^1 is outdated

    Consider upgrading to the latest version to get all the fixes and improvements.

    thiserror versions

  • Dependency which ^7 is outdated

    Consider upgrading to the latest version to get all the fixes and improvements.

    which versions

  • Dependency x25519-dalek ^2 is a bit outdated

    Consider upgrading to the latest version to get all the fixes and improvements.

    x25519-dalek versions

• zim-studio

  • 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 pulldown-cmark ^0.12 is significantly outdated

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

    pulldown-cmark versions

  • Imprecise dependency requirement clap = ^4

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

    clap versions

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["audio-player", "wav", "music", "zim", "sidecar"] (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 'ratatui' 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 'ratatui', 'fuzzy-matcher', 'crossterm', 'hound', 'claxon', 'simplelog', 'rodio', 'serde_json', 'log' may have been unintentional.

    Crate features

• zim-studio, gamecode-mcp2

  • Dependency serde_yaml ^0.9 has issues

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

    serde_yaml crate

• lisplings

  • Dependency notify ^7 is significantly outdated

    Consider upgrading to the latest version to get all the fixes and improvements.

    notify versions

  • Dependency colored ^2 is outdated

    Consider upgrading to the latest version to get all the fixes and improvements.

    colored versions

  • Dependency notify-debouncer-mini ^0.5 is outdated

    Consider upgrading to the latest version to get all the fixes and improvements.

    notify-debouncer-mini versions

  • Dependency toml ^0.8 is outdated

    Consider upgrading to the latest version to get all the fixes and improvements.

    toml versions

  • Missing keywords

    Help users find your crates. Add keywords = ["learning-exercise", "interactive-exercises", "lisp", "dialect", "watch"] (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.

• patch-prolog-shared

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["interning", "representation", "prolog", "atom", "codegen"] (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.

  • No readme property

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

• wscat-rs

  • Dependency tokio-tungstenite ^0.26 is significantly outdated

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

    tokio-tungstenite versions

  • Missing categories

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

    List of available categories

• flag-rs

  • Failed to verify create's content against its repository

    Verified 46 out of 66 files (includes 3 Cargo-generated).

    • warning: Crate tarball has been published from the commit 5f422d5ff0ba955f7c55c3054c2c5d3a8fe1204e, 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.
    • .gitignore does not match the repository.
    • README.md does not match the repository.
    • Cargo.toml.orig does not match the repository.
    • rust-toolchain.toml not found.
    • justfile not found.
    • .forgejo/workflows/
      • ci-linux.yml not found.
      • release.yml not found.
    • benchmark.rs does not match the repository.
    • docs/
      • ARCHITECTURE.md does not match the repository.
      • ROADMAP.md does not match the repository.
    • src/
      • lib.rs does not match the repository.
      • command.rs does not match the repository.
      • flag.rs does not match the repository.
      • shell.rs does not match the repository.
      • string_pool.rs does not match the repository.
      • terminal.rs does not match the repository.
      • completion_cache.rs does not match the repository.
      • completion_timeout.rs does not match the repository.
      • completion_format.rs does not match the repository.
      • error.rs does not match the repository.

    Fetched https://github.com/navicore/flag-rs.git b823304c340612d92c696abb5c990309acffe9d1.

    Checked on 2026-08-02

    Forum thread

• seq-repl

  • Internal error

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

• patch-prolog-repl

  • Internal error

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

• patch-prolog-frontend

  • Internal error

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

• seq-lsp

  • Internal error

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

• seq-compiler

  • Internal error

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

• seq-runtime

  • Internal error

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

• patch-rexx

  • Internal error

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

• patch-prolog-lsp

  • Internal error

    We couldn't check this crate at this time, because: Crate needed for the dashboard Origin( lib.rs/crates/patch-prolog-lsp ). Please try again later.

• patch-prolog-compiler

  • Internal error

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

• patch-prolog-runtime

  • Internal error

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

• patch-prolog-core

  • Internal error

    We couldn't check this crate at this time, because: Crate needed for the dashboard Origin( lib.rs/crates/patch-prolog-core ). Please try again later.

• navipod

  • Internal error

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

• seq-tui

  • Internal error

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

• dotspace

  • Internal error

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

• triples

  • Internal error

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

• k8p

  • Internal error

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

• navactor

  • Internal error

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

No issues found in: vim-line seq-core lots-of-names cemc dotparser

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