# jsdoc3 mit Homebrew, Nix installieren

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

## Installation

```sh
sudo av install brew:jsdoc3
```

Weitere Installationsbefehle:

### macOS

- Homebrew (100%):

```sh
brew install jsdoc3
```

  Evidenz: local Homebrew formula metadata

### Linux

- Nix (92%):

```sh
nix profile install nixpkgs#jsdoc
```

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

## Paketfakten

- **Paketschlüssel:** brew:jsdoc3
- **Paketmanager:** Homebrew
- **Version:** 4.0.5
- **Quellzusammenfassung:** API documentation generator for JavaScript
- **Homepage:** <https://jsdoc.app/>
- **Generiert:** 2026-08-03T19:37:03+00:00

## Executables

- jsdoc (Alias)

## Installationsverhalten

- Bottle: nicht verfügbar

## Version und Aktualität

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

JSDoc is the long-running documentation-generator line for JavaScript source comments: a command-line tool scans `/** ... */` annotations and emits browsable API documentation. The Homebrew `jsdoc3` formula name reflects the JSDoc 3 generation, which moved the tool into the Node.js and npm ecosystem while preserving the older JavaDoc-inspired annotation culture.

### Projektgeschichte

The JSDoc project traces its modern implementation to Michael Mathews and contributors; the JSDoc repository states copyright beginning in 2011, and its change history starts with version 3.0.0. The documentation describes JSDoc 3 as an API documentation generator for JavaScript, similar to Javadoc and phpDocumentor, with comments stored beside the source code.

JSDoc 3 became the package-manager-facing generation: installable through npm and Homebrew, runnable as `jsdoc`, and configurable with JSON or JavaScript configuration files. Later 3.x releases tracked JavaScript syntax changes, including ES2015 classes, modules, async functions, generators, and Babel-era parsing support. JSDoc 4.0.0 in November 2022 adopted semantic versioning and removed the `taffydb` dependency, marking a cleanup of the older template-data model.

### Adoptionsgeschichte

JSDoc was adopted both as a documentation generator and as a comment syntax understood by editors, build tools, templates, and downstream processors. The project README lists community templates, Grunt and Gulp integrations, a GitHub Action, and tools such as `jsdoc-to-markdown`, which shows the package's role as an ecosystem hub rather than a single output format.

The package remained useful even as TypeScript grew: JSDoc comments became a bridge for JavaScript projects that wanted better generated docs, editor hints, or type-aware tooling without rewriting code as TypeScript.

### Wie es verwendet wird

Typical usage is to install `jsdoc`, run it against JavaScript source files, and optionally supply a configuration file such as `conf.json` or `conf.js` to control source paths, plugins, templates, and output. By default the tool writes generated documentation into an `out` directory unless a destination option is provided.

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

For package-maintainer culture, `jsdoc3` is a classic example of a formula name encoding a major upstream generation. It also represents the era when JavaScript documentation tooling moved from browser/Rhino-adjacent tooling into npm-driven command-line workflows, while still producing plain static documentation that Unix package managers could ship.

### Zeitleiste

- 2011: JSDoc copyright and the GitHub-hosted JSDoc 3 generation begin according to the upstream README.
- 2012: JSDoc 3.0.0 appears as the first version covered by the upstream change history.
- 2017: JSDoc 3.5.0 switches to the Babylon parser and expands support for newer JavaScript syntax.
- 2019: JSDoc 3.6.0 adds Node.js 12 compatibility and recognizes documented Closure Compiler tags.
- 2022: JSDoc 4.0.0 adopts semantic versioning and removes the `taffydb` package.

### Related projects

- JSDoc's syntax was inspired by JavaDoc-style documentation. Its ecosystem includes templates such as DocStrap, minami, docdash, and better-docs, build integrations for Grunt and Gulp, and converters such as `jsdoc-to-markdown`.

### Quellen

- <https://github.com/jsdoc/jsdoc>
- <https://github.com/jsdoc/jsdoc/blob/main/CHANGES.md>
- <https://jsdoc.app/>
- <https://jsdoc.app/about-configuring-jsdoc>
- <https://jsdoc.app/about-getting-started>


## 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: conf.json, conf.js
## Andere Paketmanager-Einträge

- Nix - jsdoc: installed executable or alias match | nixpkgs package indexes: pkgs/by-name/js/jsdoc/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/jsdoc3.yml](https://github.com/mxcl/pkgdb/blob/main/combined/jsdoc3.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