Fluent Logger is used in Python projects. A Python logging handler for Fluentd event collector 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.
A Python logging handler for Fluentd event collector
fluent-logger declares 1 direct runtime dependency on PyPI. Each one is resolved into the full dependency tree below:
Beyond its direct dependencies, fluent-logger 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 fluent-logger, expand any node on demand, and understand the full set of code that ships when you run pip install fluent-logger.
PyDeps checks fluent-logger 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 fluent-logger version is safe to install before you ship.
fluent-logger is distributed under the Unknown license. PyDeps also shows the license of every dependency in the tree so you can audit license compatibility across your whole fluent-logger install, not just the top-level package.
Install from PyPI with pip install fluent-logger. For offline or air-gapped environments, PyDeps can download fluent-logger 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 fluent-logger — the PyPI packages that list fluent-logger as a requirement. Reverse dependencies are a strong signal of how widely a package is trusted and how disruptive a breaking change would be.