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.

• hydris

  • Failed to verify create's content against its repository

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

    • warning: The crates.io package has no information about its path inside its repository.
    • warning: Could not discover crate's location in its repository (via tags).
      • Make sure the repository URL in Cargo.toml is correct
    • warning: There is no matching git tag containing version '0.1.0'.
    • error: Manifest properties don't match: Existence of [lib] inconsistent: published=true; orig=false.

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

    • Cargo.lock exists, but elsewhere in the repo.
    • Cargo.toml exists, but elsewhere in the repo.
    • Makefile does not match the repository.
    • lib.rs exists, but elsewhere in the repo.
    • src/gen/
      • timeline.rs exists, but elsewhere in the repo.
      • world.rs exists, but elsewhere in the repo.

    Fetched https://github.com/projectqai/proto.git 21dee9751da215e9cea23eeaf33b240f17409880.

    Checked on 2026-03-15

    This check is experimental.

    Forum thread

  • Dependency prost ^0.13 is outdated

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

    prost versions

  • Dependency prost-types ^0.13 is outdated

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

    prost-types versions

  • Dependency tonic ^0.12 is outdated

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

    tonic versions

  • Dependency tonic-build ^0.12 is outdated

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

    tonic-build versions

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["hardware-support"] 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 = ["protobuf", "grpc", "grpc-protobuf", "sensors", "accept"] (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.

• tinylogger

  • README missing from the repository

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

  • Missing keywords

    Help users find your crates. Add keywords = ["env-logger", "semi-compatible", "logging"] (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.

• pug

  • Latest stable release is old

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

    If the crate is truly stable, why not make a 1.0.0 release?

    Maintenance status field docs

• mtdparts

  • README missing from the repository

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

  • Missing keywords

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

• tinylogger, mtdparts, gcmap, axon

  • Missing categories

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

    List of available categories

• gcmap

  • README missing from the repository

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

  • Missing keywords

    Help users find your crates. Add keywords = ["marker", "hash-map", "remove", "dropped", "external"] (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.

• rsmt2-zz

  • Dependency error-chain ^0 has issues

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

    error-chain crate

  • Latest stable release is old

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

    Maintenance status field docs

  • Imprecise dependency requirement error-chain = ^0

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

    error-chain versions

• carrier-build

  • 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 proc-macro2 ^0.4.9 is significantly outdated

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

    proc-macro2 versions

  • Dependency prost-build ^0.4.0 is significantly outdated

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

    prost-build versions

  • Dependency quote ^0.6.5 is significantly outdated

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

    quote 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 = ["carrier", "iot", "generic", "secure", "system"] (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.

• tinylogger, mtdparts, gcmap, carrier-build, interfaces2, failure_derive_without_backtrace

  • Latest stable release is old

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

    Maintenance status field docs

• tinylogger, mtdparts, gcmap, carrier-build, failure_derive_without_backtrace, osaka-dns, axon

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

• gcmap, carrier-build, interfaces2, failure_derive_without_backtrace

  • The Cargo package has no git commit information

    Before publishing a package, make sure all packaged files are committed to the repository, and there are no "dirty" files. Push this commit to crate's public repository.

    To protect against supply chain attacks similar to CVE-2024-3094, lib.rs will soon start flagging non-reproducible packages without public source code as suspicious. Currently only git repositories are supported (but may be hosted anywhere, not just GitHub). If you'd like a different SCM supported, please file a feature request.

    More info

• interfaces2

  • Reported security advisory RUSTSEC-2021-0002

    interfaces2 is unmaintained, use interfaces instead

    All crate audits

  • Dependency handlebars ^0.29 is significantly outdated

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

    handlebars versions

  • Dependency nix ^0.10 is significantly outdated

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

    nix versions

  • Dependency bitflags ^1.0 is outdated

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

    bitflags versions

  • Imprecise dependency requirement cc = ^1

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

    cc versions

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["network-interface", "networking", "system-interface", "documentation", "interoperating"] (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.

• tinylogger, rsmt2-zz, interfaces2, osaka-dns

  • License MIT/Apache-2.0 is not in SPDX syntax

    Use OR instead of /.

    SPDX license list

• failure_derive_without_backtrace

  • Dependency proc-macro2 ^0.4.8 is significantly outdated

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

    proc-macro2 versions

  • Dependency quote ^0.6.3 is significantly outdated

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

    quote versions

  • Dependency syn ^0.14.4 is significantly outdated

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

    syn versions

  • Dependency synstructure ^0.9.0 is significantly outdated

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

    synstructure versions

• axon

  • README missing from the repository

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

  • Dependency nix ^0.15 is significantly outdated

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

    nix versions

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

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

  • Using outdated edition for no reason

    We estimate that this crate requires at least Rust 1.63, which is newer than the last 2015-edition compiler. You can upgrade without breaking any compatibility. Run cargo fix --edition and update edition="…" in Cargo.toml.

    Using the latest edition helps avoid old quirks of the compiler, and ensures Rust code has consistent syntax and behavior across all projects.

    The Edition Guide

• osaka-dns

  • 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

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["osaka", "async-for-noise", "look", "building-block", "continuations"] (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.

  • Using outdated edition for no reason

    We estimate that this crate requires at least Rust 1.38, which is newer than the last 2015-edition compiler. You can upgrade without breaking any compatibility. Run cargo fix --edition and update edition="…" in Cargo.toml.

    The Edition Guide

• futurize

  • Missing categories

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

    List of available categories

  • README missing from the repository

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

  • Dependency futures ^0.1.23 has issues

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

    futures crate

  • The Cargo package has no git commit information

    Before publishing a package, make sure all packaged files are committed to the repository, and there are no "dirty" files. Push this commit to crate's public repository.

    More info

  • Missing keywords

    Help users find your crates. Add keywords = ["future", "boilerplate", "worker", "codgen"] (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.

• osaka-macros

  • Dependency proc-macro2 ^0.4 is significantly outdated

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

    proc-macro2 versions

  • Dependency quote ^0.6.10 is significantly outdated

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

    quote versions

  • Dependency syn ^0.15.22 is significantly outdated

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

    syn versions

  • License MIT/Apache-2.0 is not in SPDX syntax

    Use OR instead of /.

    SPDX license list

• futurize-derive

  • README missing from the repository

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

  • Dependency heck ^0.3.0 is significantly outdated

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

    heck versions

  • Dependency proc-macro2 ^0.4.12 is significantly outdated

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

    proc-macro2 versions

  • Dependency quote ^0.6.6 is significantly outdated

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

    quote versions

  • Dependency syn ^0.14.8 is significantly outdated

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

    syn versions

  • The Cargo package has no git commit information

    Before publishing a package, make sure all packaged files are committed to the repository, and there are no "dirty" files. Push this commit to crate's public repository.

    More info

• osaka-macros, futurize, futurize-derive, identitykit

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

• identitykit

  • Crate contains junk files

    The crate contains boilerplate Rust files with no real functionality.

• osaka

  • Internal error

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

• carrier

  • Internal error

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

• devguard-genesis

  • Internal error

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

• elfkit

  • Internal error

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

• failure_without_backtrace

  • Internal error

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

• carrier-cli

  • Internal error

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

• ceramic

  • Internal error

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

No issues found in: zz

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