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