# docfx を Homebrew, chocolatey, Nix, scoop でインストール

docfx のインストール経路、実行ファイル、メタデータ、AI エージェント向けセキュリティノートを確認します。

## インストール

```sh
sudo av install brew:docfx
```

追加のインストールコマンド:

### macOS

- Homebrew (100%):

```sh
brew install docfx
```

  証拠: local Homebrew formula metadata

### Linux

- Nix (92%):

```sh
nix profile install nixpkgs#docfx
```

  証拠: nixpkgs package indexes: pkgs/by-name/do/docfx/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

### Windows

- Chocolatey (92%):

```sh
choco install docfx
```

  証拠: Chocolatey community package catalog: docfx from http://community.chocolatey.org/api/v2/Packages?$filter=IsLatestVersion&$select=Id&$top=1000&$skiptoken='11','dispcalgui.install'

- Scoop (92%):

```sh
scoop install main/docfx
```

  証拠: Scoop official bucket manifest trees: bucket/docfx.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1

## パッケージ情報

- **パッケージキー:** brew:docfx
- **パッケージマネージャ:** Homebrew
- **バージョン:** 2.78.5
- **ソース概要:** Tools for building and publishing API documentation for .NET projects
- **ホームページ:** <https://dotnet.github.io/docfx/>
- **リポジトリ:** <https://github.com/dotnet/docfx>
- **生成日時:** 2026-08-03T19:37:03+00:00

## 実行可能ファイル

- docfx (エイリアス)

## インストール挙動

- Bottle: 利用不可

## バージョンと鮮度

- ページ生成日: 2026-08-03
- マネージャ版: 2.78.5
## プロジェクトの歴史と使われ方

DocFX is a static documentation generator best known for combining Markdown content with generated .NET API reference documentation.

Its story is tied to Microsoft documentation: it grew as an open-source documentation engine, was associated with Microsoft Docs and Microsoft Learn workflows, and later continued as a .NET Foundation/community-driven project after Microsoft Learn stopped using the public project.

### プロジェクトの歴史

The GitHub release history reaches back to 2015-era 0.x releases, followed by a long 2.x line used by .NET projects for API docs and technical documentation sites.

DocFX's public identity emphasizes static-site generation plus API reference extraction for .NET, REST API documentation, landing pages, and Markdown documentation.

A later v3 branch was used internally for Microsoft Learn work, while public package notes and repository text state that Microsoft Learn no longer uses docfx and the project is planned to continue as community-driven under the .NET Foundation.

### 採用の歴史

DocFX was adopted by .NET library and platform projects because it could generate reference documentation from assemblies or source comments while hosting conceptual docs in the same site.

It is distributed through NuGet and packaged by Homebrew, Chocolatey, Scoop, and Nix, covering both developer-local and CI documentation builds.

### 使われ方

A typical project keeps a docfx.json config file, runs docfx metadata/build/serve commands, and publishes the generated static site to GitHub Pages, Azure Static Web Apps, or another static host.

The tool is especially useful when API reference and hand-written Markdown must cross-link in one documentation site.

### パッケージ好きにとっての重要性

DocFX is a major example of docs-as-code moving from bespoke vendor documentation systems into normal package-manager-installed CLI workflows.

Its Microsoft Learn transition is historically interesting because it left a widely used open-source tool with a community maintenance path after the largest original user moved on.

### タイムライン

- 2015: early v0.x DocFX releases appeared on GitHub.
- 2016-2021: the 2.x release line matured into the common public DocFX generation path for .NET projects.
- 2018: Microsoft Learn's On .NET show introduced DocFX as an open-source static site generator for source-code and Markdown documentation.
- 2021-2022: v3 prerelease work existed, while public notes later said the v3 branch was privatized for Microsoft Learn.
- 2022 onward: Microsoft Learn stopped using the public docfx project and DocFX continued as a .NET Foundation/community-driven project.
- 2025-2026: the public 2.x line continues to receive compatibility and maintenance releases.

### Related projects

- Related documentation generators include Sandcastle, Doxygen, Sphinx, MkDocs, Docusaurus, Docsy, and Microsoft Learn's current internal documentation systems.
- DocFX depends conceptually on .NET XML documentation comments, Roslyn metadata extraction, Markdown processing, templates, and static-site publishing workflows.

### ソース

- <https://github.com/dotnet/docfx>
- <https://dotnet.github.io/docfx/>
- <https://dotnet.github.io/docfx/docs/basic-concepts.html>
- <https://learn.microsoft.com/en-us/shows/on-dotnet/intro-to-docfx>
- <https://www.nuget.org/packages/docfx/2.62.2>
- <https://www.nuget.org/packages/Docfx.Dotnet/>
- <https://github.com/dotnet/docfx/releases>
- <https://learn.microsoft.com/en-us/iis/contribute>


## セキュリティノート

narrow executable package without higher-risk signals.

- **Geiger リスク:** グリーン / 低
- 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: ./docfx.json
## 他のパッケージマネージャ記録

- Nix - docfx: normalized package name match | nixpkgs package indexes: pkgs/by-name/do/docfx/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
- Chocolatey - docfx: normalized package name match | Chocolatey community package catalog: docfx from http://community.chocolatey.org/api/v2/Packages?$filter=IsLatestVersion&$select=Id&$top=1000&$skiptoken='11','dispcalgui.install'
- Scoop - main/docfx: normalized package name match | Scoop official bucket manifest trees: bucket/docfx.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1


## Combined YAML source

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


## ソース

- 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
