Dingtalk Stream is used in Python projects. A Python library for sending messages to DingTalk chatbot 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.
A Python library for sending messages to DingTalk chatbot
dingtalk-stream declares 3 direct runtime dependencies on PyPI. Each one is resolved into the full dependency tree below:
Beyond its direct dependencies, dingtalk-stream 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 dingtalk-stream, expand any node on demand, and understand the full set of code that ships when you run pip install dingtalk-stream.
PyDeps checks dingtalk-stream 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 dingtalk-stream version is safe to install before you ship.
dingtalk-stream 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 dingtalk-stream install, not just the top-level package.
Install from PyPI with pip install dingtalk-stream. For offline or air-gapped environments, PyDeps can download dingtalk-stream 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 dingtalk-stream — the PyPI packages that list dingtalk-stream as a requirement. Reverse dependencies are a strong signal of how widely a package is trusted and how disruptive a breaking change would be.