Grpc Stubs is used in Python projects. Mypy stubs for gRPC It has 1 direct runtime dependency. Check its dependency graph on PyDeps to understand the full transitive dependency tree, reverse dependents, known CVEs, and license compatibility before installing.
Mypy stubs for gRPC
grpc-stubs declares 1 direct runtime dependency on PyPI. Each one is resolved into the full dependency tree below:
Beyond its direct dependencies, grpc-stubs can pull in further packages through its dependency tree. PyDeps resolves the entire chain from PyPI and deps.dev so you can see every transitive (nested) dependency of grpc-stubs, expand any node on demand, and understand the full set of code that ships when you run pip install grpc-stubs.
PyDeps checks grpc-stubs and every package in its dependency tree against the OSV vulnerability database in real time. For each CVE you can see the severity, the affected version ranges, and the first fixed version, so you know exactly which grpc-stubs version is safe to install before you ship.
grpc-stubs is distributed under the MIT license. PyDeps also shows the license of every dependency in the tree so you can audit license compatibility across your whole grpc-stubs install, not just the top-level package.
Install from PyPI with pip install grpc-stubs. For offline or air-gapped environments, PyDeps can download grpc-stubs together with every resolved dependency as wheel files in a single bundle, matched to your target Python version and operating system.
Switch to the dependents view to see the reverse dependencies of grpc-stubs — the PyPI packages that list grpc-stubs as a requirement. Reverse dependencies are a strong signal of how widely a package is trusted and how disruptive a breaking change would be.