Openmed is used in Python projects. OpenMed delivers state-of-the-art biomedical and clinical LLMs that rival proprietary enterprise stacks, unifying model discovery, advanced extractions, and one-line orchestration. It has 3 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.
OpenMed delivers state-of-the-art biomedical and clinical LLMs that rival proprietary enterprise stacks, unifying model discovery, advanced extractions,...
openmed declares 3 direct runtime dependencies on PyPI. Each one is resolved into the full dependency tree below:
Beyond its direct dependencies, openmed 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 openmed, expand any node on demand, and understand the full set of code that ships when you run pip install openmed.
PyDeps checks openmed 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 openmed version is safe to install before you ship.
openmed is distributed under the Apache-2.0 license. PyDeps also shows the license of every dependency in the tree so you can audit license compatibility across your whole openmed install, not just the top-level package.
Install from PyPI with pip install openmed. For offline or air-gapped environments, PyDeps can download openmed 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 openmed — the PyPI packages that list openmed as a requirement. Reverse dependencies are a strong signal of how widely a package is trusted and how disruptive a breaking change would be.