Publicsuffix2 is used in Python projects. Get a public suffix for a domain name using the Public Suffix List. Forked from and using the same API as the publicsuffix package. 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.
Get a public suffix for a domain name using the Public Suffix List. Forked from and using the same API as the publicsuffix package.
publicsuffix2 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, publicsuffix2 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 publicsuffix2, expand any node on demand, and understand the full set of code that ships when you run pip install publicsuffix2.
PyDeps checks publicsuffix2 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 publicsuffix2 version is safe to install before you ship.
publicsuffix2 is distributed under the MIT and MPL-2.0 license. PyDeps also shows the license of every dependency in the tree so you can audit license compatibility across your whole publicsuffix2 install, not just the top-level package.
Install from PyPI with pip install publicsuffix2. For offline or air-gapped environments, PyDeps can download publicsuffix2 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 publicsuffix2 — the PyPI packages that list publicsuffix2 as a requirement. Reverse dependencies are a strong signal of how widely a package is trusted and how disruptive a breaking change would be.