Django Pglock is used in Python projects. Postgres locking routines and lock table access. 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.
Postgres locking routines and lock table access.
django-pglock declares 2 direct runtime dependencies on PyPI. Each one is resolved into the full dependency tree below:
Beyond its direct dependencies, django-pglock 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 django-pglock, expand any node on demand, and understand the full set of code that ships when you run pip install django-pglock.
PyDeps checks django-pglock 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 django-pglock version is safe to install before you ship.
django-pglock is distributed under the BSD-3-Clause license. PyDeps also shows the license of every dependency in the tree so you can audit license compatibility across your whole django-pglock install, not just the top-level package.
Install from PyPI with pip install django-pglock. For offline or air-gapped environments, PyDeps can download django-pglock 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 django-pglock — the PyPI packages that list django-pglock as a requirement. Reverse dependencies are a strong signal of how widely a package is trusted and how disruptive a breaking change would be.