Dirty Equals is used in Python projects. Doing dirty (but extremely useful) things with equals. It has no required runtime dependencies, making it lightweight to install. Check its dependency graph on PyDeps to understand the full transitive dependency tree, reverse dependents, known CVEs, and license compatibility before installing.
Doing dirty (but extremely useful) things with equals.
dirty-equals has no required runtime dependencies. Installing it adds no transitive packages to your environment, which keeps installs small and minimizes the supply-chain surface you need to audit.
Beyond its direct dependencies, dirty-equals 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 dirty-equals, expand any node on demand, and understand the full set of code that ships when you run pip install dirty-equals.
PyDeps checks dirty-equals 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 dirty-equals version is safe to install before you ship.
dirty-equals 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 dirty-equals install, not just the top-level package.
Install from PyPI with pip install dirty-equals. For offline or air-gapped environments, PyDeps can download dirty-equals 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 dirty-equals — the PyPI packages that list dirty-equals as a requirement. Reverse dependencies are a strong signal of how widely a package is trusted and how disruptive a breaking change would be.