Apeye is used in Python projects. Handy tools for working with URLs and APIs. It has 4 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.
Handy tools for working with URLs and APIs.
apeye declares 4 direct runtime dependencies on PyPI. Each one is resolved into the full dependency tree below:
Beyond its direct dependencies, apeye 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 apeye, expand any node on demand, and understand the full set of code that ships when you run pip install apeye.
PyDeps checks apeye 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 apeye version is safe to install before you ship.
apeye is distributed under the GNU Lesser General Public License v3 or later (LGPLv3+). PyDeps also shows the license of every dependency in the tree so you can audit license compatibility across your whole apeye install, not just the top-level package.
Install from PyPI with pip install apeye. For offline or air-gapped environments, PyDeps can download apeye 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 apeye — the PyPI packages that list apeye as a requirement. Reverse dependencies are a strong signal of how widely a package is trusted and how disruptive a breaking change would be.