Automic VaultAutomic Vault

brew

Installer docfx avec Homebrew, chocolatey, Nix, scoop

Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de docfx pour les workflows d'agents IA.

installation

Commandes d'installation supplémentaires

macOS

Homebrewvérifié · 100%
brew install docfx

local Homebrew formula metadata

Linux

Nixvérifié · 92%
nix profile install nixpkgs#docfx

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

Windows

Chocolateyvérifié · 92%
choco install docfx

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

Scoopvérifié · 92%
scoop install main/docfx

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

aperçu

Résumé du paquet

Tools for building and publishing API documentation for .NET projects

historique

Historique du projet et usages

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.

Historique du projet

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.

Historique d'adoption

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.

Modes d'utilisation

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.

Pourquoi les passionnés de paquets s'y intéressent

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.

Chronologie

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

posture de sécurité

Niveau de risque : vert

narrow executable package without higher-risk signals.

Classificateur de risque

risque vert · confiance faible · appliance

Pourquoi

  • narrow executable package without higher-risk signals

Signaux

  • metadata:no-higher-risk-signals

Comportement d'installation

  • Aucun hook post-install Homebrew n’est enregistré dans les métadonnées de formule.
  • Les métadonnées de bottle Homebrew sont disponibles pour 6 plateformes.
  • S’installe avec 1 dépendances d’exécution.
  • Les métadonnées de compilation listent 1 dépendances de compilation.

Revue recommandée

Avant une utilisation sans surveillance par un agent, vérifiez si l'outil lit des identifiants en clair, écrit un état distant, publie des artefacts ou lance des 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

exécutables

Exécutables installés

CommandeTypeExpositionNote
docfxcliexécutable global

fraîcheur

Version et fraîcheur

Ces signaux séparent l'âge de génération de la page, l'activité du gestionnaire de paquets et la comparaison avec les versions amont. Un retard de version n'est signalé que lorsqu'une URL de preuve et des versions comparables sont présentes.

page générée2026-07-25
version du gestionnaire2.78.5
gestionnaire mis à jour
données localesOK
amontà jour
dernière version détectéev2.78.5

https://github.com/dotnet/docfx

  • infoNo package-manager update timestamp was available.confiance faible

métadonnées d'installation

Métadonnées du paquet

Clé du paquetbrew:docfx
Version2.78.5
Gestionnaire de paquetsHomebrew
Page du gestionnaire de paquetshttps://formulae.brew.sh/formula/docfx
Page d'accueilhttps://dotnet.github.io/docfx/
Dépôthttps://github.com/dotnet/docfx
Docs amonthttps://dotnet.github.io/docfx
LicenceMIT
Archive sourcehttps://github.com/dotnet/docfx/archive/refs/tags/v2.78.5.tar.gz
Dépendancesdotnet
Dépendances de compilationnode
Bouteilledisponible (sur arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
post-install Homebrewnon défini
Serviceaucun déclaré

faits du registre

Détails de la base source

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

correspondances dans les bases sources

Autres enregistrements de gestionnaires de paquets

Les correspondances proviennent d’index externes de gestionnaires de paquets et restent séparées des liens de paquets Automic Vault locaux.

Nix95%

docfx

nix profile install nixpkgs#docfx
  • normalized package name match
  • Correspondance par : 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
  • Correspondance par : 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
  • Correspondance par : 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

piste source

Généré depuis les données du dépôt

Cette page est servie par av-web depuis l'artéfact SQLite privé des paquets généré par scripts/generate-pkg-sqlite.py.

Sources utilisées

  • 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