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