Cle is used in Python projects. CLE Loads Everything (at least, many binary formats!) and provides a pythonic interface to analyze what they are and what they would look like in memory. It has 10 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.
CLE Loads Everything (at least, many binary formats!) and provides a pythonic interface to analyze what they are and what they would look like in memory.
cle declares 10 direct runtime dependencies on PyPI. Each one is resolved into the full dependency tree below:
Beyond its direct dependencies, cle 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 cle, expand any node on demand, and understand the full set of code that ships when you run pip install cle.
PyDeps checks cle 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 cle version is safe to install before you ship.
cle is distributed under the BSD-2-Clause license. PyDeps also shows the license of every dependency in the tree so you can audit license compatibility across your whole cle install, not just the top-level package.
Install from PyPI with pip install cle. For offline or air-gapped environments, PyDeps can download cle 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 cle — the PyPI packages that list cle as a requirement. Reverse dependencies are a strong signal of how widely a package is trusted and how disruptive a breaking change would be.