pkg.soopen package index

brew / 排名 5507

使用 Homebrew, Nix 安装 jsdoc3

查看 jsdoc3 的安装路径、可执行文件、元数据以及面向 AI 代理工作流的安全说明。

安装

其他安装命令

macOS

Homebrew已验证 · 100%
brew install jsdoc3

local Homebrew formula metadata

Linux

Nix已验证 · 92%
nix profile install nixpkgs#jsdoc

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

概览

软件包摘要

API documentation generator for JavaScript

命令和别名

  • jsdoc

历史

项目历史与用法

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.

项目历史

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.

采用历史

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.

使用方式

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.

为什么软件包爱好者会关心

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.

时间线

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

安全态势

风险级别:绿色

narrow executable package without higher-risk signals.

风险分类器

绿色 风险 · 低 置信度 · appliance

原因

  • narrow executable package without higher-risk signals

信号

  • metadata:no-higher-risk-signals

安装行为

  • 未记录 Homebrew bottle 元数据。

建议审查

在无人值守的代理使用前,请检查该工具是否读取明文凭据、写入远程状态、发布制品或调用插件。

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

可执行文件

已安装的可执行文件

命令类型暴露范围备注
jsdoc可执行文件已索引可执行文件从本地可执行文件索引发现。

新鲜度

版本和新鲜度

这些信号区分页生成时间、软件包管理器活动和上游发布比较。只有存在证据 URL 和可比较版本时,才会提示版本落后。

页面生成时间2026-08-03
管理器版本4.0.5
管理器更新时间
本地数据未知
上游不可用
检测到的最新版本未检测到
  • OK没有生成新鲜度警告。

安装元数据

软件包元数据

软件包键brew:jsdoc3
版本4.0.5
软件包管理器Homebrew
主页https://jsdoc.app/
Bottle未记录
服务未声明

源数据库匹配

其他软件包管理器记录

匹配项来自外部软件包管理器索引,并与本地 Automic Vault 软件包链接分开显示。

Nix92%

jsdoc

nix profile install nixpkgs#jsdoc
  • installed executable or alias match
  • 匹配方式: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

来源线索

由仓库数据生成

此页面由 av-webscripts/generate-pkg-sqlite.py 生成的私有软件包 SQLite 工件提供。

使用的来源

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