# Install dcd with Homebrew

Auto-complete program for the D programming language. Version 0.16.2 via Homebrew; verified from local package data.

## Install

```sh
sudo av install brew:dcd
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install dcd
```

  Evidence: provider-native install command

## Package facts

- **Package key:** brew:dcd
- **Package manager:** Homebrew
- **Version:** 0.16.2
- **Source summary:** Auto-complete program for the D programming language
- **Homepage:** <https://github.com/dlang-community/DCD>
- **Repository:** <https://github.com/dlang-community/dcd>
- **Generated:** 2026-08-03T00:40:33+00:00

## Executables

- dcd-client (alias)
- dcd-server (alias)

## Install behavior

- Bottle: not available

## Freshness

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

DCD, the D Completion Daemon, is an autocomplete program for the D programming language. Its README positions it as editor infrastructure rather than an IDE: a server caches imported files and computes completion data, while a client is called by editor integrations or the command line.

### Project history

The official GitHub repository was created in 2013 under the D language community organization. The README documents a client/server design, Unix-domain socket defaults on Unix-like systems, TCP socket support, and setup paths through Homebrew, source builds, or Dub.

### Adoption history

DCD sits in the era before language-server-protocol tooling fully standardized editor integration. Its adoption came through editor scripts and plugins for D programmers, with the README pointing users to a wiki page for IDE and editor support and the input package facts showing availability in Homebrew, MacPorts, and Arch packaging.

### How it is used

Package users install DCD to give lightweight editors D-aware completion, call tips, symbol locations, and import completion without installing a full IDE. The server process is started before editing, and editor plugins usually invoke dcd-client on source buffers.

### Why package nerds care

DCD is a classic small-language tooling package: two command-line programs, a daemon protocol, editor hooks, and a package-manager install path. It matters to package nerds because it shows how autocomplete tooling was distributed before every language tool became an LSP server.

### Timeline

- 2013: Official GitHub repository created.
- 2010s: README documents Homebrew, Git/Make, and Dub installation paths.
- 2025: Official GitHub API metadata shows repository activity continuing into December 2025.

### Related projects

- The README points IDE users to D editor integrations; in the wider D ecosystem, Dub and D compilers provide the build/runtime context that DCD expects.

### Sources

- <https://github.com/dlang-community/DCD>
- <https://raw.githubusercontent.com/dlang-community/DCD/master/README.md>
- <https://api.github.com/repos/dlang-community/DCD>


## Security Notes

broad file, network, media, or database tool signal. generalized runtime or code generation signal.

- **Geiger risk:** yellow / medium
- broad file, network, media, or database tool signal
- generalized runtime or code generation signal


## Combined YAML source

View the package source record on GitHub. [combined/dcd.yml](https://github.com/automic-vault/db/blob/main/combined/dcd.yml)


## Sources

- Nucleus package database
- Geiger risk classifier
- curated package history
- pkgdb category and tag curation