Automic VaultAutomic Vault

brew

docfx mit Homebrew, chocolatey, Nix, scoop installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install docfx

local Homebrew formula metadata

Linux

Nixverifiziert · 92%
nix profile install nixpkgs#docfx

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

Windows

Chocolateyverifiziert · 92%
choco install docfx

Chocolatey community package catalog · docfx · Quelle: community.chocolatey.org

Scoopverifiziert · 92%
scoop install main/docfx

Scoop official bucket manifest trees · bucket/docfx.json · Quelle: api.github.com

Überblick

Paketzusammenfassung

Tools for building and publishing API documentation for .NET projects

Verlauf

Projektgeschichte und Nutzung

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.

Projektgeschichte

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.

Adoptionsgeschichte

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.

Wie es verwendet wird

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.

Warum Paket-Nerds sich dafür interessieren

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.

Zeitleiste

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

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 6 Plattformziele verfügbar.
  • Installiert mit 1 Laufzeitabhängigkeiten.
  • Build-Metadaten listen 1 Build-Abhä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
./docfx.json

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
docfxcliglobales 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-25
Manager-Version2.78.5
Manager aktualisiert
lokale DatenOK
Upstreamaktuell
neueste erkannte Versionv2.78.5

https://github.com/dotnet/docfx

  • InfoNo package-manager update timestamp was available.niedrig Konfidenz

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:docfx
Version2.78.5
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/docfx
Homepagehttps://dotnet.github.io/docfx/
Repositoryhttps://github.com/dotnet/docfx
Upstream-Dokumentationhttps://dotnet.github.io/docfx
LizenzMIT
Quellarchivhttps://github.com/dotnet/docfx/archive/refs/tags/v2.78.5.tar.gz
Abhängigkeitendotnet
Build-Abhängigkeitennode
Bottleverfügbar (auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namedocfx
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.

Nix95%

docfx

nix profile install nixpkgs#docfx
  • normalized package name match
  • Abgeglichen nach: Docfx
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/do/docfx/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
Chocolatey95%

docfx

choco install docfx
  • normalized package name match
  • Abgeglichen nach: Docfx
Chocolatey community package catalog · community.chocolatey.org · Chocolatey community package catalog: docfx from http://community.chocolatey.org/api/v2/Packages?$filter=IsLatestVersion&$select=Id&$top=1000&$skiptoken='11','dnspy'
Scoop95%

main/docfx

scoop install main/docfx
  • normalized package name match
  • Abgeglichen nach: Docfx
Scoop official bucket manifest trees · api.github.com · Scoop official bucket manifest trees: bucket/docfx.json from https://api.github.com/repos/ScoopInstaller/Main/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