Impacket is used in Python projects. Network protocols Constructors and Dissectors It has 10 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.
Network protocols Constructors and Dissectors
impacket declares 10 direct runtime dependencies on PyPI. Each one is resolved into the full dependency tree below:
Beyond its direct dependencies, impacket 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 impacket, expand any node on demand, and understand the full set of code that ships when you run pip install impacket.
PyDeps checks impacket 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 impacket version is safe to install before you ship.
impacket is distributed under the Apache modified license. PyDeps also shows the license of every dependency in the tree so you can audit license compatibility across your whole impacket install, not just the top-level package.
Install from PyPI with pip install impacket. For offline or air-gapped environments, PyDeps can download impacket 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 impacket — the PyPI packages that list impacket as a requirement. Reverse dependencies are a strong signal of how widely a package is trusted and how disruptive a breaking change would be.