Crewai Core is used in Python projects. Shared utilities for CrewAI — version, paths, user-data, telemetry, printer. It has 12 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.
Shared utilities for CrewAI — version, paths, user-data, telemetry, printer.
crewai-core declares 12 direct runtime dependencies on PyPI. Each one is resolved into the full dependency tree below:
Beyond its direct dependencies, crewai-core 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 crewai-core, expand any node on demand, and understand the full set of code that ships when you run pip install crewai-core.
PyDeps checks crewai-core 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 crewai-core version is safe to install before you ship.
crewai-core 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 crewai-core install, not just the top-level package.
Install from PyPI with pip install crewai-core. For offline or air-gapped environments, PyDeps can download crewai-core 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 crewai-core — the PyPI packages that list crewai-core as a requirement. Reverse dependencies are a strong signal of how widely a package is trusted and how disruptive a breaking change would be.