Fqdn is used in Python projects. Validates fully-qualified domain names against RFC 1123, so that they are acceptable to modern bowsers 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.
Validates fully-qualified domain names against RFC 1123, so that they are acceptable to modern bowsers
fqdn declares 1 direct runtime dependency on PyPI. Each one is resolved into the full dependency tree below:
Beyond its direct dependencies, fqdn 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 fqdn, expand any node on demand, and understand the full set of code that ships when you run pip install fqdn.
PyDeps checks fqdn 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 fqdn version is safe to install before you ship.
fqdn is distributed under the MPL 2.0 license. PyDeps also shows the license of every dependency in the tree so you can audit license compatibility across your whole fqdn install, not just the top-level package.
Install from PyPI with pip install fqdn. For offline or air-gapped environments, PyDeps can download fqdn 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 fqdn — the Python packages that list fqdn as a requirement. Reverse dependencies are a strong signal of how widely a package is trusted and how disruptive a breaking change would be.