Backcall Dependency Graph

Backcall is used in Python projects. Specifications for callback functions passed in to an API 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.

What is Backcall used for?

Specifications for callback functions passed in to an API

Direct dependencies

Backcall has no required runtime dependencies. A dependency-free package keeps installs small and reduces the supply-chain surface area you need to audit.

Transitive dependencies

Beyond its direct dependencies, Backcall pulls in further packages through its dependency tree. PyDeps walks the entire chain from PyPI and deps.dev so you can see every transitive (nested) dependency, expand any node on demand, and understand the full set of code that ships when you install Backcall.

Dependency risk and maintenance

Backcall is distributed under the BSD License license. Use the vulnerability panel, powered by the OSV database, to check whether Backcall or anything in its dependency tree has known CVEs before you ship, and review the license of every dependency to confirm compatibility with your project.

How to read the dependency graph

In the interactive graph each node is a package and each edge is a version constraint. Expand a node to load its subdependencies, switch to the dependents view to see which packages rely on Backcall, and download Backcall together with all of its dependencies as wheels for offline or air-gapped installs.

Related packages

PyDeps