Timing Asgi is used in Python projects. ASGI middleware to emit timing metrics with something like statsd It has no required runtime dependencies, making it lightweight to install. Check its dependency graph on PyDeps to understand the full transitive dependency tree, reverse dependents, known CVEs, and license compatibility before installing.
ASGI middleware to emit timing metrics with something like statsd
timing-asgi has no required runtime dependencies. Installing it adds no transitive packages to your environment, which keeps installs small and minimizes the supply-chain surface you need to audit.
Beyond its direct dependencies, timing-asgi 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 timing-asgi, expand any node on demand, and understand the full set of code that ships when you run pip install timing-asgi.
PyDeps checks timing-asgi 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 timing-asgi version is safe to install before you ship.
timing-asgi 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 timing-asgi install, not just the top-level package.
Install from PyPI with pip install timing-asgi. For offline or air-gapped environments, PyDeps can download timing-asgi 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 timing-asgi — the PyPI packages that list timing-asgi as a requirement. Reverse dependencies are a strong signal of how widely a package is trusted and how disruptive a breaking change would be.