Pygdbmi is used in Python projects. Parse gdb machine interface output with Python It has no required runtime dependencies, making it lightweight to install. Check its dependency graph on PyDeps to understand the full transitive dependency tree, reverse dependents, known CVEs, and license compatibility before installing.
Parse gdb machine interface output with Python
pygdbmi has no required runtime dependencies. Installing it adds no transitive packages to your environment, which keeps installs small and minimizes the supply-chain surface you need to audit.
Beyond its direct dependencies, pygdbmi 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 pygdbmi, expand any node on demand, and understand the full set of code that ships when you run pip install pygdbmi.
PyDeps checks pygdbmi 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 pygdbmi version is safe to install before you ship.
pygdbmi 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 pygdbmi install, not just the top-level package.
Install from PyPI with pip install pygdbmi. For offline or air-gapped environments, PyDeps can download pygdbmi 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 pygdbmi — the PyPI packages that list pygdbmi as a requirement. Reverse dependencies are a strong signal of how widely a package is trusted and how disruptive a breaking change would be.