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.

• googapis

  • Dependency prost 0.9.0 is significantly outdated

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

    prost versions

  • Dependency prost-types 0.9.0 is significantly outdated

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

    prost-types versions

  • Dependency tonic 0.6.1 is significantly outdated

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

    tonic 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

  • 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

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

• google-authz

  • Latest prerelease 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").

    Users pay attention to the latest release date. Even if the crate is perfectly fine as-is, users may not know that.

    Maintenance status field docs

  • Dependency hyper-rustls 0.23 is significantly outdated

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

    hyper-rustls versions

  • Dependency gcemeta 0.2 is a bit outdated

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

    gcemeta versions

  • Dependency hyper 0.14 is outdated

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

    hyper versions

  • Dependency jsonwebtoken 8.1 is outdated

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

    jsonwebtoken versions

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

• gcemeta, google-authz

  • Dependency thiserror 1.0 is a bit outdated

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

    thiserror versions

• openrtb-native1

  • Dependency openrtb2 0.2 is slightly outdated

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

    openrtb2 versions

• google-api-proto, chatwork, gouth, json-ext, default-ext, iso-4217

  • Internal error

    We couldn't check this crate at this time, because: deadline has elapsed. Please try again later.

No issues found in: adstxt vast4 openrtb2

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