# ghorg mit Homebrew, Nix, scoop installieren

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

## Installation

```sh
sudo av install brew:ghorg
```

Weitere Installationsbefehle:

### macOS

- Homebrew (100%):

```sh
brew install ghorg
```

  Evidenz: local Homebrew formula metadata

### Linux

- Nix (92%):

```sh
nix profile install nixpkgs#ghorg
```

  Evidenz: nixpkgs package indexes: pkgs/by-name/gh/ghorg/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

### Windows

- Scoop (92%):

```sh
scoop install main/ghorg
```

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

## Paketfakten

- **Paketschlüssel:** brew:ghorg
- **Paketmanager:** Homebrew
- **Version:** 1.11.14
- **Quellzusammenfassung:** Quickly clone an entire org's or user's repositories into one directory
- **Homepage:** <https://github.com/gabrie30/ghorg>
- **Repository:** <https://github.com/gabrie30/ghorg>
- **Zuletzt aktualisiert:** 2026-07-25T20:55:22-04:00
- **Generiert:** 2026-08-03T19:37:03+00:00

## Executables

- ghorg (Alias)

## Installationsverhalten

- Bottle: nicht verfügbar

## Version und Aktualität

- Seite generiert: 2026-08-03
- Manager-Version: 1.11.14
## Projektgeschichte und Nutzung

ghorg is a Go command-line tool for cloning all repositories from a source-control organization or user into one local directory.

### Projektgeschichte

The GitHub repository for ghorg was created in 2018, and the project settled around a narrow developer-operations job: turn a hosted source-control namespace into a local tree of Git repositories. Its README describes default behavior that either clones missing repositories or updates existing local clones with pull and clean operations.

The project evolved beyond GitHub-only organization cloning into a provider-oriented tool. Official documentation lists support for GitHub, GitLab, Bitbucket, Gitea, and SourceHut, with separate setup and example pages for provider-specific authentication, API limits, and self-hosted base URLs.

### Adoptionsgeschichte

ghorg's adoption is concentrated among teams and operators that need local snapshots of many repositories at once rather than one-off clones. The README's installation section documents prebuilt binaries, Homebrew, Mise, Go installation, Docker, and Windows support, matching its role as a cross-platform CLI utility.

### Wie es verwendet wird

Practitioners use ghorg to clone an organization's repositories for code search, onboarding, audits, backups, and scripted maintenance. Typical use starts with a provider token in the ghorg YAML configuration or a command-line flag, then runs a clone or reclone operation against an organization, user, or group.

### Warum Paket-Nerds sich dafür interessieren

Package nerds care about ghorg because it automates the otherwise repetitive edge between package-manager install culture and source-control inventory work: install one small binary, point it at a namespace, and get a reproducible local checkout layout for analysis or backup.

### Zeitleiste

- 2018: GitHub repository created.
- 2018: v1.0.6 published on GitHub Releases.
- 2019: README screenshot and CLI examples document the bulk-clone workflow.
- 2020s: Documentation covers GitHub, GitLab, Bitbucket, Gitea, and SourceHut providers.

### Related projects

- ghorg sits beside Git hosting APIs, GitHub Enterprise and GitLab self-managed deployments, XDG-style CLI configuration, and command-line search tools such as grep, ack, and The Silver Searcher.

### Quellen

- <https://api.github.com/repos/gabrie30/ghorg>
- <https://github.com/gabrie30/ghorg>
- <https://github.com/gabrie30/ghorg#readme>
- <https://github.com/gabrie30/ghorg/releases/tag/v1.0.6>


## Sicherheitshinweise

Für ghorg wurde kein passendes lokales Secret-Handling-Manifest gefunden. Nucleus-Paketmetadaten bleiben hier veröffentlicht, damit künftige Abdeckung eine stabile Paket-URL hat.



## 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: ~/.config/ghorg/conf.yaml, $XDG_CONFIG_HOME/ghorg/conf.yaml

## Credential files

- Unix: ~/.config/ghorg/conf.yaml, $XDG_CONFIG_HOME/ghorg/conf.yaml
## Andere Paketmanager-Einträge

- Nix - ghorg: normalized package name match | nixpkgs package indexes: pkgs/by-name/gh/ghorg/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
- Scoop - main/ghorg: normalized package name match | Scoop official bucket manifest trees: bucket/ghorg.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/ghorg.yml](https://github.com/mxcl/pkgdb/blob/main/combined/ghorg.yml)


## Quellen

- 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