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