Robotframework Assertion Engine is used in Python projects. Generic way to create meaningful and easy to use assertions for the Robot Framework libraries. It has 2 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.
Generic way to create meaningful and easy to use assertions for the Robot Framework libraries.
robotframework-assertion-engine declares 2 direct runtime dependencies on PyPI. Each one is resolved into the full dependency tree below:
Beyond its direct dependencies, robotframework-assertion-engine 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 robotframework-assertion-engine, expand any node on demand, and understand the full set of code that ships when you run pip install robotframework-assertion-engine.
PyDeps checks robotframework-assertion-engine 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 robotframework-assertion-engine version is safe to install before you ship.
robotframework-assertion-engine 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 robotframework-assertion-engine install, not just the top-level package.
Install from PyPI with pip install robotframework-assertion-engine. For offline or air-gapped environments, PyDeps can download robotframework-assertion-engine 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 robotframework-assertion-engine — the PyPI packages that list robotframework-assertion-engine as a requirement. Reverse dependencies are a strong signal of how widely a package is trusted and how disruptive a breaking change would be.