Click Aliases is used in Python projects. Add (mutiple) aliases to a click group or command 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.
Add (mutiple) aliases to a click group or command
click-aliases declares 1 direct runtime dependency on PyPI. Each one is resolved into the full dependency tree below:
Beyond its direct dependencies, click-aliases 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 click-aliases, expand any node on demand, and understand the full set of code that ships when you run pip install click-aliases.
PyDeps checks click-aliases 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 click-aliases version is safe to install before you ship.
click-aliases is distributed under the MIT license. PyDeps also shows the license of every dependency in the tree so you can audit license compatibility across your whole click-aliases install, not just the top-level package.
Install from PyPI with pip install click-aliases. For offline or air-gapped environments, PyDeps can download click-aliases 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 click-aliases — the PyPI packages that list click-aliases as a requirement. Reverse dependencies are a strong signal of how widely a package is trusted and how disruptive a breaking change would be.