Mypy Boto3 Bedrock Agentcore is used in Python projects. Type annotations for boto3 BedrockAgentCore 1.43.35 service generated with mypy-boto3-builder 8.12.0 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.
Type annotations for boto3 BedrockAgentCore 1.43.35 service generated with mypy-boto3-builder 8.12.0
mypy-boto3-bedrock-agentcore declares 1 direct runtime dependency on PyPI. Each one is resolved into the full dependency tree below:
Beyond its direct dependencies, mypy-boto3-bedrock-agentcore 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 mypy-boto3-bedrock-agentcore, expand any node on demand, and understand the full set of code that ships when you run pip install mypy-boto3-bedrock-agentcore.
PyDeps checks mypy-boto3-bedrock-agentcore 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 mypy-boto3-bedrock-agentcore version is safe to install before you ship.
mypy-boto3-bedrock-agentcore 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 mypy-boto3-bedrock-agentcore install, not just the top-level package.
Install from PyPI with pip install mypy-boto3-bedrock-agentcore. For offline or air-gapped environments, PyDeps can download mypy-boto3-bedrock-agentcore 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 mypy-boto3-bedrock-agentcore — the PyPI packages that list mypy-boto3-bedrock-agentcore as a requirement. Reverse dependencies are a strong signal of how widely a package is trusted and how disruptive a breaking change would be.