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.

• protoc-plugin-by-closure

  • Published crate doesn't match its repository

    Verified 11 out of 12 files (includes 3 Cargo-generated).

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

    • Cargo.lock not found.
    • README.md not found.

    Looked for the crate in lib/. Fetched https://github.com/wada314/protoc-plugin-by-closure.git 58224d784f8ec9606872bc49c1baa5314c514e24.

    Checked on 2025-10-19

    This check is experimental.

    Forum thread

  • 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 = ["encoding"] 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 = ["compiler-plugin", "protoc", "protobuf", "closures", "proto-path"] (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 'tempfile' 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 'tempfile' may have been unintentional.

    Crate features

• protobuf-core

  • 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 2025-10-19

    Forum thread

  • Could not fetch repository

    We've had trouble cloning git repo from https://github\.com/wada314/protobuf\-core\.git

    At the moment we only support git, and attempt fetching when we index a new release. Cloning is necessary for lib.rs to gather data that is missing on crates.io, e.g. to correctly resolve relative URLs in README files, which depend on repository layout and non-standard URL schemes of repository hosts.

  • 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 = ["encoding"] to the Cargo.toml.

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["protocols-buffer", "constant", "primitive", "utility", "define"] (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.

• protoc-plugin-proxy

  • 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 7 out of 8 files (includes 2 Cargo-generated).

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

    • README.md not found.

    Looked for the crate in proxy/. Fetched https://github.com/wada314/protoc-plugin-by-closure.git f1c49582bde30b0345443cb0c6c4d2df282ef299.

    Checked on 2025-09-14

    Forum thread

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

    Detecting docs.rs

  • Dependency protoc-plugin-bin 0.1.2 is outdated

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

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

    protoc-plugin-bin versions

  • Missing keywords

    Help users find your crates. Add keywords = ["proxy", "protoc-plugin-bin", "proxy-for-protoc-plugin-bin", "binary", "internal"] (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.

• once-list2

  • Published crate doesn't match its repository

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

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

    • Cargo.lock not found.
    • README.md not found.

    Fetched https://github.com/wada314/once-list.git 39cd5a99bd7ce793b96899984ee193c20f254f4b.

    Checked on 2025-03-02

    Forum thread

  • Dependency allocator-api2 0.2.21 is slightly outdated

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

    allocator-api2 versions

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["linked-list", "once-cell", "vec", "value", "once-list"] (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.

• puroro-codegen

  • Latest stable release is old

    It's been over 2 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").

    Nightly crates tend to have a short lifespan. We're delisting them if they're not updated frequently.

    Maintenance status field docs

  • Dependency prettyplease 0.1.23 is significantly outdated

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

    prettyplease versions

  • Dependency syn 1.0 is significantly outdated

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

    syn versions

  • Dependency itertools 0.10 is outdated

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

    itertools versions

  • 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 = ["protobuf", "compiler-plugin", "puroro", "google", "directory"] (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.

• protoc-plugin-bin

  • 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 6 out of 7 files (includes 3 Cargo-generated).

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

    • Cargo.lock not found.
    • README.md not found.

    Looked for the crate in bin/. Fetched https://github.com/wada314/protoc-plugin-by-closure.git 58224d784f8ec9606872bc49c1baa5314c514e24.

    Checked on 2025-10-19

    Forum thread

  • Missing keywords

    Help users find your crates. Add keywords = ["protoc-plugin-by-closure", "document", "manual"] (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.

• puroro

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["protobuf", "google", "compiler", "generated", "proto-file"] (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.

• puroro, protobuf-core, puroro-codegen

  • Dependency thiserror 1.0 is outdated

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

    thiserror versions

• derive-insert

  • Published crate doesn't match its repository

    Partially verified 9 files (includes 2 Cargo-generated).

    Fetched https://github.com/wada314/derive-insert.git 933a38a77d01486e7ba7c769c21bf0b3771d1573.

    Checked on 2024-12-01

    Forum thread

  • Missing categories

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

    List of available categories

• puroro-codegen, puroro-protobuf-compiled, puroro-plugin

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

• puroro-protobuf-compiled

  • Dependency puroro 0.10.0 is a bit outdated

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

    puroro 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 = ["puroro", "google", "protocols-buffer", "user", "ui"] (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.

• puroro-plugin

  • Dependency puroro-codegen 0.10.0 is slightly outdated

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

    puroro-codegen 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 = ["protocols-buffer", "puroro", "google", "compiler", "compiler-plugin"] (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 issues found in: quither quither-proc-macros cached-pair derive-insert-impl

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