# Installer gor avec Homebrew

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

## installation

```sh
sudo av install brew:gor
```

Commandes d'installation supplémentaires:

### macOS

- Homebrew (100%):

```sh
brew install gor
```

  Preuve: local Homebrew formula metadata

## Faits du paquet

- **Clé du paquet:** brew:gor
- **Gestionnaire de paquets:** Homebrew
- **Version:** 1.3.3
- **Résumé source:** Real-time HTTP traffic replay tool written in Go
- **Page d'accueil:** <https://goreplay.org>
- **Dépôt:** <https://github.com/probelabs/goreplay>
- **Dernière mise à jour:** 2026-07-05T00:14:30+09:00
- **Généré:** 2026-08-03T19:37:03+00:00

## exécutables

- gor (alias)

## Comportement d'installation

- Bouteille: non disponible

## Version et fraîcheur

- page générée: 2026-08-03
- version du gestionnaire: 1.3.3
## Historique du projet et usages

GoReplay, installed as `gor`, is a traffic capture and replay tool for testing systems with real HTTP traffic. It sits in the package-manager world as a single executable that can be dropped onto production-like hosts to record traffic, replay it to staging, or build load-test streams.

### Historique du projet

The repository was created in 2013 by Leonid Bugaev and was long known in package managers by the shorter command name `gor`. Official materials describe GoReplay as an open-source network monitoring and traffic replay tool that records live traffic for shadowing, load testing, monitoring, and detailed analysis.

The core design avoided acting as a proxy in the request path. Instead, GoReplay listens in the background on network interfaces, a design choice the README presents as a way to avoid changing production infrastructure beyond running the daemon.

The project later developed a commercial GoReplay PRO offering for features such as binary protocols, cloud storage, TCP session replication, and commercial-friendly licensing, while the open-source command remained the package-manager artifact.

### Historique d'adoption

The README lists production users and adopters such as GOV.UK, The Guardian, TomTom, 3scale, OpinionLab, TubeMogul, Videology, ForeksMobile, and Granify. That kind of adoption made GoReplay a familiar name in traffic-shadowing and deployment-validation conversations.

Homebrew packages the command as `gor`, preserving the older concise executable name even though the project branding is GoReplay. That mismatch is part of its package history.

### Modes d'utilisation

A basic capture command listens on a port with `--input-raw` and writes to stdout, a file, or an HTTP output. The documented staging replay pattern is `gor --input-raw :80 --output-http http://staging.example`.

GoReplay can also save requests to a file and replay them later while preserving timing characteristics. That makes it useful for regression testing, load testing, and deployment confidence checks using observed traffic rather than synthetic request sets.

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

GoReplay is significant because it packages a production-adjacent network tool as a portable Go binary. The Homebrew formula name `gor` is a reminder that package-manager identity can lag or differ from project branding.

It also illustrates a recurring ops-tool pattern: one executable with composable input and output flags, where package managers provide installability and the operational topology lives in command arguments.

### Chronologie

- 2013: GoReplay repository created.
- 2010s: Project documents capture and replay workflows around `--input-raw`, `--output-http`, and file outputs.
- 2010s: README lists production users including GOV.UK, The Guardian, TomTom, and 3scale.
- 2020s: Documentation continues under the GoReplay brand while Homebrew keeps the `gor` package name.

### Related projects

- GoReplay PRO is the commercial extension line described by the project.
- tcpdump is a conceptual comparison in the docs for passive traffic capture.
- Traffic shadowing, load testing, and staging replay workflows are the operational ecosystem around GoReplay.

### Sources

- <https://docs.goreplay.org/>
- <https://docs.goreplay.org/untitled/capturing-and-replaying-traffic>
- <https://docs.goreplay.org/untitled/saving-and-replaying-from-file>
- <https://github.com/buger/goreplay>
- <https://leonsbox.com/projects/goreplay/>


## Notes de sécurité

broad file, network, media, or database tool signal. generalized runtime or code generation signal.

- **Risque Geiger:** yellow / moyen
- broad file, network, media, or database tool signal
- generalized runtime or code generation signal


## Combined YAML source

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


## Sources

- pkg.so package database
- Geiger risk classifier
- curated package history
- pkgdb category and tag curation
- cross-ecosystem install command graph