Angr is used in Python projects. A multi-architecture binary analysis toolkit, with the ability to perform dynamic symbolic execution and various static analyses on binaries It has 26 direct runtime dependencies. Check its dependency graph on PyDeps to understand the full transitive dependency tree, reverse dependents, known CVEs, and license compatibility before installing.
A multi-architecture binary analysis toolkit, with the ability to perform dynamic symbolic execution and various static analyses on binaries
angr declares 26 direct runtime dependencies on PyPI. Each one is resolved into the full dependency tree below:
Beyond its direct dependencies, angr 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 angr, expand any node on demand, and understand the full set of code that ships when you run pip install angr.
PyDeps checks angr 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 angr version is safe to install before you ship.
angr is distributed under the BSD-2-Clause license. PyDeps also shows the license of every dependency in the tree so you can audit license compatibility across your whole angr install, not just the top-level package.
Install from PyPI with pip install angr. For offline or air-gapped environments, PyDeps can download angr 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 angr — the PyPI packages that list angr as a requirement. Reverse dependencies are a strong signal of how widely a package is trusted and how disruptive a breaking change would be.