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.

• googletest

  • Imprecise dependency requirement anyhow = 1

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

    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

• protobuf-parse

  • Locked dependency version protobuf =3.7.2

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    protobuf versions

  • Dependency which 4.0 is outdated

    Consider upgrading to 7.0.3 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.

    which versions

  • Failed to verify create's content against its repository

    Partially verified 47 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 not found.

    Looked for the crate in protobuf-parse/. Fetched https://github.com/stepancheg/rust-protobuf.git tagged v3.7.2 (4cb84f305c05f0376ff51b555a2740c5251c1280).

    Checked on 2025-04-29

    This check is experimental.

    Forum thread

  • Missing keywords

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

• protobuf-json-mapping

  • Locked dependency version protobuf =3.7.2

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    protobuf versions

  • Missing keywords

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

• protobuf-support

  • Missing keywords

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

• protobuf-support, protobuf-parse, protobuf-json-mapping

  • Dependency thiserror 1.0.30 is a bit outdated

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

    thiserror versions

• protobuf-support, protobuf-parse, protobuf-json-mapping

  • 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

• test_data_passing_crate

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