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