Clr Loader is used in Python projects. Generic pure Python loader for .NET runtimes 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.
Generic pure Python loader for .NET runtimes
clr-loader declares 1 direct runtime dependency on PyPI. Each one is resolved into the full dependency tree below:
Beyond its direct dependencies, clr-loader 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 clr-loader, expand any node on demand, and understand the full set of code that ships when you run pip install clr-loader.
PyDeps checks clr-loader 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 clr-loader version is safe to install before you ship.
clr-loader 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 clr-loader install, not just the top-level package.
Install from PyPI with pip install clr-loader. For offline or air-gapped environments, PyDeps can download clr-loader 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 clr-loader — the PyPI packages that list clr-loader as a requirement. Reverse dependencies are a strong signal of how widely a package is trusted and how disruptive a breaking change would be.