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