Eth Account is used in Python projects. eth-account: Sign Ethereum transactions and messages with local private keys It has 10 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.
eth-account: Sign Ethereum transactions and messages with local private keys
eth-account declares 10 direct runtime dependencies on PyPI. Each one is resolved into the full dependency tree below:
Beyond its direct dependencies, eth-account 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 eth-account, expand any node on demand, and understand the full set of code that ships when you run pip install eth-account.
PyDeps checks eth-account 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 eth-account version is safe to install before you ship.
eth-account 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 eth-account install, not just the top-level package.
Install from PyPI with pip install eth-account. For offline or air-gapped environments, PyDeps can download eth-account 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 eth-account — the PyPI packages that list eth-account as a requirement. Reverse dependencies are a strong signal of how widely a package is trusted and how disruptive a breaking change would be.