Pylint Django is used in Python projects. A Pylint plugin to help Pylint understand the Django web framework 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 Pylint plugin to help Pylint understand the Django web framework
pylint-django declares 2 direct runtime dependencies on PyPI. Each one is resolved into the full dependency tree below:
Beyond its direct dependencies, pylint-django 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 pylint-django, expand any node on demand, and understand the full set of code that ships when you run pip install pylint-django.
PyDeps checks pylint-django 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 pylint-django version is safe to install before you ship.
pylint-django is distributed under the GNU General Public License v2 or later (GPLv2+). PyDeps also shows the license of every dependency in the tree so you can audit license compatibility across your whole pylint-django install, not just the top-level package.
Install from PyPI with pip install pylint-django. For offline or air-gapped environments, PyDeps can download pylint-django 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 pylint-django — the PyPI packages that list pylint-django as a requirement. Reverse dependencies are a strong signal of how widely a package is trusted and how disruptive a breaking change would be.