Automic VaultAutomic Vault

brew

jsdoc3 mit Homebrew, Nix installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install jsdoc3

local Homebrew formula metadata

Linux

Nixverifiziert · 92%
nix profile install nixpkgs#jsdoc

nixpkgs package indexes · pkgs/by-name/js/jsdoc/package.nix · Quelle: api.github.com

Überblick

Paketzusammenfassung

API documentation generator for JavaScript

Befehle und Aliase

  • jsdoc

Verlauf

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`.

Sicherheitslage

Risikostufe: grün

narrow executable package without higher-risk signals.

Risikoklassifikator

grün Risiko · niedrig Konfidenz · appliance

Warum

  • narrow executable package without higher-risk signals

Signale

  • metadata:no-higher-risk-signals

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Homebrew-Bottle-Metadaten sind für 1 Plattformziele verfügbar.
  • Installiert mit 1 Laufzeitabhängigkeiten.

Empfohlene Prüfung

Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.

local files

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

Config paths the tool may read or write during local use.

Unix
conf.jsonconf.js

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
jsdoccliglobales Executable

Aktualität

Version und Aktualität

Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.

Seite generiert2026-07-08
Manager-Version4.0.5
Manager aktualisiert
lokale DatenOK
Upstreamnot checked
neueste erkannte Versionnicht erkannt

https://jsdoc.app/

  • InfoNo package-manager update timestamp was available.niedrig Konfidenz
  • InfoRelease/tag comparison is only available for GitHub repositories.https://jsdoc.app/none Konfidenz

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:jsdoc3
Version4.0.5
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/jsdoc3
Homepagehttps://jsdoc.app/
Repositoryhttps://github.com/jsdoc/jsdoc
Upstream-Dokumentationhttps://jsdoc.app/
LizenzApache-2.0
Quellarchivhttps://registry.npmjs.org/jsdoc/-/jsdoc-4.0.5.tgz
Abhängigkeitennode
Bottleverfügbar (auf all)
Homebrew post-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namejsdoc3
Version Scheme0
Revision0
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • stable

Source-Datenbank-Treffer

Andere Paketmanager-Einträge

Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.

Nix92%

jsdoc

nix profile install nixpkgs#jsdoc
  • installed executable or alias match
  • Abgeglichen nach: Jsdoc
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/js/jsdoc/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

Quellspur

Aus Repository-Daten generiert

Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.

Verwendete Quellen

  • Geiger risk classifier
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated configuration and credential file locations
  • curated package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment