This release has been yanked by its maintainers, and will be ignored by installers, except when explicitly specified.
Consider using release 0.1.1 instead.
grpchealth-py
An idiomatic Python implementation of gRPC's health checking protocol
(grpc.health.v1), built on protobuf-py and
connectrpc. Modeled on Buf's Go reference implementation,
grpchealth-go.
Since the health service here is just a ConnectASGIApplication like any
other, it works over whichever of connectrpc's protocols your own services
already speak -- Connect, gRPC, and gRPC-Web -- with no extra configuration.
Install
uv add grpchealth-py
Usage
mount_health_handler() takes a Checker -- optionally one that also
implements Watcher, to support the streaming Watch RPC -- and returns a
ready-to-mount ConnectASGIApplication:
from starlette.applications import Starlette
from starlette.routing import Mount
from grpchealth.checker import StaticChecker
from grpchealth.server import mount_health_handler
health = mount_health_handler(StaticChecker("acme.greet.v1.GreetService"))
app = Starlette(routes=[Mount(health.path, app=health)])
Watch is a server-streaming RPC, which benefits from an HTTP/2-capable ASGI
server. As of this writing, pyvoy is the server most reliably
passing the Connect conformance suite's HTTP/2 and streaming tests, so it's
the recommended way to serve app above:
import asyncio
import pyvoy
async def main() -> None:
server = pyvoy.PyvoyServer("myapp:app", port=8080)
await server.start()
await server.wait()
asyncio.run(main())
You aren't required to use pyvoy -- any ASGI server with working HTTP/2 and
streaming support will do -- but not every ASGI server reliably supports both
today.
Client
Client calls the gRPC health-checking API against a server. It structurally
satisfies Checker (and, via watch, Watcher), so it can be used anywhere
either is expected:
import asyncio
from grpchealth.checker import CheckRequest
from grpchealth.client import Client
async def main() -> None:
async with Client("http://localhost:8080") as client:
response = await client.check(
CheckRequest(service="acme.greet.v1.GreetService")
)
print(response.status)
async for response in client.watch(
CheckRequest(service="acme.greet.v1.GreetService")
):
print(response.status)
asyncio.run(main())
Development
uv run -- buf generate # regenerate src/grpchealth/_gen from the upstream schema
uv run pytest
Metadata
Release files for grpchealth-py 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| grpchealth_py-0.1.0.tar.gz | 12.4 kB | With provenance | Details for grpchealth_py-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| grpchealth_py-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for grpchealth_py-0.1.0-py3-none-any.whl |
Total release size: 28.4 kB
Release files / grpchealth_py-0.1.0.tar.gz
| Download URL | grpchealth_py-0.1.0.tar.gz |
|---|---|
| Size | 12.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2afa54f09cf8205e05e9fcc517737d84a4c52ac04b6117a5cf9747ca78b5058c
|
|
BLAKE2b-256 checksum How to use checksums |
6d505ef464d6c8efd281c60976484d119ae077441a4874b8ddba0bd7e8a0bd92
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.
Transparency logRelease files / grpchealth_py-0.1.0-py3-none-any.whl
| Download URL | grpchealth_py-0.1.0-py3-none-any.whl |
|---|---|
| Size | 16.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
96296858443d3ece389c42df567914c42979a6726070bf6d3d02c3fa6a240e7c
|
|
BLAKE2b-256 checksum How to use checksums |
3757106da2621fc7d204ccbcc7a02123b9d4adecc4739d205d334a5c4aa14cea
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.
Transparency logSecurity for grpchealth-py 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for grpchealth_py-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.