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