# dtop mit Homebrew, Nix installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für dtop in AI-Agent-Workflows.

## Installation

```sh
sudo av install brew:dtop
```

Weitere Installationsbefehle:

### macOS

- Homebrew (100%):

```sh
brew install dtop
```

  Evidenz: local Homebrew formula metadata

### Linux

- Nix (92%):

```sh
nix profile install nixpkgs#dtop
```

  Evidenz: nixpkgs package indexes: pkgs/by-name/dt/dtop/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

## Paketfakten

- **Paketschlüssel:** brew:dtop
- **Paketmanager:** Homebrew
- **Version:** 0.7.11
- **Quellzusammenfassung:** Terminal dashboard for Docker monitoring across multiple hosts
- **Homepage:** <https://dtop.dev/>
- **Repository:** <https://github.com/amir20/dtop>
- **Zuletzt aktualisiert:** 2026-07-27T18:28:47Z
- **Generiert:** 2026-08-03T19:37:03+00:00

## Executables

- dtop (Alias)

## Installationsverhalten

- Bottle: nicht verfügbar

## Version und Aktualität

- Seite generiert: 2026-08-03
- Manager-Version: 0.7.11
## Projektgeschichte und Nutzung

dtop is a Rust terminal dashboard for Docker container monitoring. It focuses on real-time CPU, memory, network, status, and log visibility across local and remote Docker hosts.

### Projektgeschichte

The public repository was created in 2025 by Amir Salihefendic, the same developer behind Dozzle. The README positions dtop as a terminal companion to Docker operations, with multi-host support over local sockets, SSH, TCP, and TLS, plus integration points for Dozzle log views.

### Adoptionsgeschichte

dtop is young, but it entered several distribution channels quickly: Homebrew, GitHub release installers, Docker images, Nix, and Cargo. The README explicitly recommends Homebrew for macOS or Linux because the project is in active development with frequent updates.

### Wie es verwendet wird

A typical user runs `dtop` against the local Docker daemon or passes one or more `--host` values for remote hosts. The optional YAML config lets users persist hosts, Dozzle URLs, filters, icon mode, and display preferences.

### Warum Paket-Nerds sich dafür interessieren

dtop matters to package nerds as part of the current wave of single-binary Rust TUIs: it overlaps with Docker dashboards, log viewers, and terminal observability tools, while still being distributed through classic package managers and container images.

### Zeitleiste

- 2025: Public amir20/dtop repository created.
- 2025: Crates.io package metadata records the `dtop` crate.
- 2025-2026: Homebrew formula distributes tagged upstream releases.

### Related projects

- The README explicitly connects dtop to Docker and Dozzle. Its feature set also overlaps with terminal monitor dashboards and container log viewers.

### Quellen

- <https://github.com/amir20/dtop>
- <https://dtop.dev/>
- <https://github.com/amir20/dtop/blob/master/README.md>
- <https://crates.io/api/v1/crates/dtop>
- <https://formulae.brew.sh/api/formula/dtop.json>


## Sicherheitshinweise

narrow executable package without higher-risk signals.

- **Geiger-Risiko:** grün / niedrig
- narrow executable package without higher-risk signals


## Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.


## Configuration files

- Unix: ./config.yaml, ./config.yml, ./.dtop.yaml, ./.dtop.yml, ~/.config/dtop/config.yaml, ~/.config/dtop/config.yml, ~/.dtop.yaml, ~/.dtop.yml
## Andere Paketmanager-Einträge

- Nix - dtop: normalized package name match | nixpkgs package indexes: pkgs/by-name/dt/dtop/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1


## Combined YAML source

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


## Quellen

- pkg.so package database
- Geiger risk classifier
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation
- external package-manager database matches
- cross-ecosystem install command graph