Pyee is used in Python projects. A rough port of Node.js's EventEmitter to Python with a few tricks of its own 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.
A rough port of Node.js's EventEmitter to Python with a few tricks of its own
pyee declares 1 direct runtime dependency on PyPI. Each one is resolved into the full dependency tree below:
Beyond its direct dependencies, pyee 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 pyee, expand any node on demand, and understand the full set of code that ships when you run pip install pyee.
PyDeps checks pyee 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 pyee version is safe to install before you ship.
pyee 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 pyee install, not just the top-level package.
Install from PyPI with pip install pyee. For offline or air-gapped environments, PyDeps can download pyee 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 pyee — the Python packages that list pyee as a requirement. Reverse dependencies are a strong signal of how widely a package is trusted and how disruptive a breaking change would be.