Enum34 is used in Python projects. Python 3.4 Enum backported to 3.3, 3.2, 3.1, 2.7, 2.6, 2.5, and 2.4 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.
Python 3.4 Enum backported to 3.3, 3.2, 3.1, 2.7, 2.6, 2.5, and 2.4
enum34 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, enum34 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 enum34, expand any node on demand, and understand the full set of code that ships when you run pip install enum34.
PyDeps checks enum34 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 enum34 version is safe to install before you ship.
enum34 is distributed under the BSD License. PyDeps also shows the license of every dependency in the tree so you can audit license compatibility across your whole enum34 install, not just the top-level package.
Install from PyPI with pip install enum34. For offline or air-gapped environments, PyDeps can download enum34 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 enum34 — the PyPI packages that list enum34 as a requirement. Reverse dependencies are a strong signal of how widely a package is trusted and how disruptive a breaking change would be.