Autopep8 is used in Python projects. A tool that automatically formats Python code to conform to the PEP 8 style guide It has 2 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 tool that automatically formats Python code to conform to the PEP 8 style guide
autopep8 declares 2 direct runtime dependencies on PyPI. Each one is resolved into the full dependency tree below:
Beyond its direct dependencies, autopep8 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 autopep8, expand any node on demand, and understand the full set of code that ships when you run pip install autopep8.
PyDeps checks autopep8 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 autopep8 version is safe to install before you ship.
autopep8 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 autopep8 install, not just the top-level package.
Install from PyPI with pip install autopep8. For offline or air-gapped environments, PyDeps can download autopep8 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 autopep8 — the PyPI packages that list autopep8 as a requirement. Reverse dependencies are a strong signal of how widely a package is trusted and how disruptive a breaking change would be.