# Install johnnydep with Homebrew

Display dependency tree of Python distribution. Version 2.1.0 via Homebrew; verified 2026-05-22.

## Install

```sh
sudo av install brew:johnnydep
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install johnnydep
```

  Evidence: local Homebrew formula metadata

## Package facts

- **Package key:** brew:johnnydep
- **Package manager:** Homebrew
- **Version:** 2.1.0
- **Source summary:** Display dependency tree of Python distribution
- **Homepage:** <https://github.com/wimglenn/johnnydep>
- **Last updated:** 2026-05-22T22:35:08Z
- **Generated:** 2026-08-03T19:37:03+00:00

## Executables

- johnnydep (alias)

## Install behavior

- Bottle: not available

## Freshness

- Page generated: 2026-08-03
- Package-manager version: 2.1.0
## Project history and usage

Johnnydep is a small Python packaging utility for pretty-printing the dependency tree of a Python distribution. Its README demonstrates resolving packages such as requests and boto3 into tree output, and it can also emit pinned dependency output for resolver-oriented workflows.

### Project history

The wimglenn/johnnydep repository was created in 2018, and PyPI records the first 0.1a0 upload on March 22, 2018. The project has stayed focused on one narrow job: ask Python packaging metadata and resolvers what a distribution depends on, then display that dependency graph in a human-readable form.

### Adoption history

Johnnydep's adoption is niche but practical: it is published on PyPI for Python users and packaged by Homebrew for command-line installation on macOS and Linux. The Homebrew formula describes the same narrow purpose and packages it with Python, libyaml, certifi, and uv-related resolver support.

### How it is used

Users run johnnydep with a distribution name to inspect immediate and transitive dependencies, summaries, and optional pinned output. It fits the debugging space between pip metadata, lockfile generation, and tools such as pipdeptree.

### Why package nerds care

Johnnydep is a package-nerd tool because it exists to make package metadata visible. It is not a general dependency manager; its value is the short feedback loop when someone wants to understand why installing one Python distribution pulls in a particular stack.

### Timeline

- 2018: The GitHub repository was created.
- 2018: Version 0.1a0 was uploaded to PyPI.
- 2026: PyPI recorded the 2.1.0 release.

### Related projects

- Related projects and standards include PyPI, Python core metadata, the Simple Repository API, wheel metadata, uv, unearth, pip, and pipdeptree.

### Sources

- <https://api.github.com/repos/wimglenn/johnnydep>
- <https://formulae.brew.sh/formula/johnnydep>
- <https://github.com/wimglenn/johnnydep>
- <https://pypi.org/pypi/johnnydep/json>


## Security Notes

narrow executable package without higher-risk signals.

- **Geiger risk:** green / low
- narrow executable package without higher-risk signals


## Combined YAML source

View the package source record on GitHub. [combined/johnnydep.yml](https://github.com/mxcl/pkgdb/blob/main/combined/johnnydep.yml)


## Sources

- pkg.so package database
- Geiger risk classifier
- curated package history
- pkgdb category and tag curation
- cross-ecosystem install command graph