Blobfile is used in Python projects. Read GCS, ABS and local paths with the same interface, clone of tensorflow.io.gfile It has 4 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.
Read GCS, ABS and local paths with the same interface, clone of tensorflow.io.gfile
blobfile declares 4 direct runtime dependencies on PyPI. Each one is resolved into the full dependency tree below:
Beyond its direct dependencies, blobfile 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 blobfile, expand any node on demand, and understand the full set of code that ships when you run pip install blobfile.
PyDeps checks blobfile 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 blobfile version is safe to install before you ship.
blobfile is distributed under the Public Domain license. PyDeps also shows the license of every dependency in the tree so you can audit license compatibility across your whole blobfile install, not just the top-level package.
Install from PyPI with pip install blobfile. For offline or air-gapped environments, PyDeps can download blobfile 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 blobfile — the PyPI packages that list blobfile as a requirement. Reverse dependencies are a strong signal of how widely a package is trusted and how disruptive a breaking change would be.