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.

• mk-rs

  • Published crate doesn't match its repository

    Verified 6 out of 7 files (includes 3 Cargo-generated).

    • warning: Crate tarball has been published from a commit that is not in the main branch (searched 3 commits deep).

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

    • GIT_HASH not found.
    • Cargo.lock not found.

    Looked for the crate in crates/mk-cli/. Fetched https://github.com/e4779/mk-rs.git tagged v0.2.4 (e7582c63d83a45b275d2dfddb951835411c6bb45).

    Checked on 2026-06-28

    This check is experimental.

    Forum thread

  • 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

  • No readme property

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

• ninep-sync

  • Failed to verify create's content against its repository

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

    • 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: Had to perform fuzzy search of the head branch due to lack of commit information in the package.
    • error: Manifest properties don't match: Number of [[bin]] inconsistent; published=0; orig=2; ed=Set(E2024).

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

    • Cargo.lock does not match the repository.
    • README.md does not match the repository.
    • Cargo.toml.orig does not match the repository.
    • lib.rs does not match the repository.
    • src/fs/
      • simple.rs exists, but elsewhere in the repo.
      • mod.rs exists, but elsewhere in the repo.
    • src/sansio/
      • mod.rs exists, but elsewhere in the repo.
      • protocol.rs exists, but elsewhere in the repo.
      • client.rs exists, but elsewhere in the repo.
      • server.rs exists, but elsewhere in the repo.
    • src/sync/
      • mod.rs exists, but elsewhere in the repo.
      • client.rs exists, but elsewhere in the repo.
      • server.rs exists, but elsewhere in the repo.
    • src/test_utils/
      • server_cases.rs exists, but elsewhere in the repo.
      • mod.rs exists, but elsewhere in the repo.
      • client_cases.rs exists, but elsewhere in the repo.
    • src/tokio/
      • client.rs exists, but elsewhere in the repo.
      • mod.rs exists, but elsewhere in the repo.
      • server.rs exists, but elsewhere in the repo.
    • src/util/
      • hook.rs exists, but elsewhere in the repo.
      • mod.rs exists, but elsewhere in the repo.
      • ram.rs exists, but elsewhere in the repo.
      • read_only.rs exists, but elsewhere in the repo.
      • local_proxy.rs exists, but elsewhere in the repo.

    Fetched https://github.com/e4779/p9-wikifs-rs.git 6419d7816cd413b9bba23c726cb6803dd7c679c7.

    Checked on 2026-07-12

    Forum thread

  • Imprecise dependency requirement bitflags = ^2

    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.

    bitflags versions

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["filesystem"] 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 = ["9p", "manpage", "labs", "bones", "protocols"] (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.

• mk-rs-core

  • No readme property

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

  • Imprecise dependency requirement regex = ^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.

    regex versions

• mk-rs-shell

  • Internal error

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

• toonq

  • Internal error

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

• mk-graph

  • Internal error

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