pkg.sopackage field notes

brew / rank 7449

Install docfx with Homebrew

Tools for building and publishing API documentation for .NET projects. Version 2.78.5 via Homebrew; verified from local package data.

install

Additional install commands

macOS

Homebrewverified · 100%
brew install docfx

provider-native install command

overview

Package summary

Tools for building and publishing API documentation for .NET projects

Commands and aliases

  • docfx

history

Project history and usage

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.

Project history

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.

Adoption history

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.

How it is used

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.

Why package nerds care

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.

Timeline

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

security posture

Risk level: green

narrow executable package without higher-risk signals.

Risk classifier

green risk · low confidence · appliance

Why

  • narrow executable package without higher-risk signals

Signals

  • metadata:no-higher-risk-signals

Install behavior

  • No Homebrew bottle metadata was recorded.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.

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
./docfx.json

executables

Installed executables

CommandKindExposureNote
docfxexecutableindexed executableDiscovered from the local executable index.

freshness

Version and freshness

These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.

page generated2026-08-03
manager version2.78.5
manager updated
local dataunknown
upstreamnot available
latest detectednot detected
  • okNo freshness warnings were generated.

install metadata

Package metadata

Package keybrew:docfx
Version2.78.5
Package managerHomebrew
Homepagehttps://dotnet.github.io/docfx/
Repositoryhttps://github.com/dotnet/docfx
Bottlenot recorded
Servicenone declared

source trail

Generated from repository data

This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.

Used sources

  • Geiger risk classifier
  • Nucleus package database
  • curated configuration and credential file locations
  • curated package history
  • pkgdb category and tag curation