# Install gor with Homebrew Real-time HTTP traffic replay tool written in Go. Version 1.3.3 via Homebrew; verified 2026-07-05. ## Install ```sh sudo av install brew:gor ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install gor ``` Evidence: local Homebrew formula metadata ## Package facts - **Package key:** brew:gor - **Package manager:** Homebrew - **Package manager page:** - **Version:** 1.3.3 - **Source summary:** Real-time HTTP traffic replay tool written in Go - **Homepage:** - **Repository:** - **Upstream docs:** - **License:** LGPL-3.0-only - **Source archive:** - **Last updated:** 2026-07-05T00:14:30+09:00 - **Generated:** 2026-07-09T07:20:21+00:00 ## Executables - gor (cli) - gor (alias) ## Build dependencies - go ## Uses from macOS - libpcap ## Install behavior - Post-install hook: not defined - Bottle: available on arm64_big_sur, arm64_linux, arm64_monterey, arm64_sequoia, arm64_sonoma, arm64_tahoe, arm64_ventura, big_sur, catalina, monterey, sonoma, ventura ## Freshness - Page generated: 2026-07-09 - Package-manager version: 1.3.3 - Package-manager updated: 2026-07-05 - Local data: ok - Upstream repository: https://github.com/probelabs/goreplay - Upstream latest detected: 1.3.3 (current) ## Project history and usage 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. ### Project history 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. ### Adoption history 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. ### How it is used 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. ### Why package nerds care 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. ### Timeline - 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 - - - - - ## Security Notes broad file, network, media, or database tool signal. generalized runtime or code generation signal. - **Geiger risk:** yellow / medium - broad file, network, media, or database tool signal - generalized runtime or code generation signal ## Source Database Details - **Source Database:** Homebrew formula API - **Tap:** homebrew/core - **Full Name:** gor - **Version Scheme:** 0 - **Revision:** 0 - **Head Version:** HEAD - **Bottle Stable Root URL:** - **Deprecated:** no - **Disabled:** no - **Keg Only:** no - **URL Keys:** head, stable ## Related links - [Secret-risk packages](https://www.automicvault.com/pkg/secret-risk-packages/) - Has protected-tool coverage, approval-gate, or non-low Geiger security signals. - [Terminal utility packages](https://www.automicvault.com/pkg/terminal-utilities/) - Matched terminal and command-line workflow metadata. - [Text processing packages](https://www.automicvault.com/pkg/text-processing-tools/) - Matched text, document, or structured-data processing metadata. - [Developer build packages](https://www.automicvault.com/pkg/developer-build-tools/) - Matched build, compiler, generator, or developer workflow metadata. - [go](https://www.automicvault.com/pkg/brew/go/) - Build dependency declared by Homebrew. - [cassowary](https://www.automicvault.com/pkg/brew/cassowary/) - Shares av.db curated category or tags: cli, developer-tools, go, http, load-testing. - [goku](https://www.automicvault.com/pkg/brew/goku/) - Shares av.db curated category or tags: cli, developer-tools, http, load-testing, testing. - [vegeta](https://www.automicvault.com/pkg/brew/vegeta/) - Shares av.db curated category or tags: cli, developer-tools, go, http, load-testing. - [artillery](https://www.automicvault.com/pkg/brew/artillery/) - Shares av.db curated category or tags: cli, developer-tools, load-testing, testing. - [bzt](https://www.automicvault.com/pkg/brew/bzt/) - Shares av.db curated category or tags: cli, developer-tools, load-testing, testing. - [counterfeiter](https://www.automicvault.com/pkg/brew/counterfeiter/) - Shares av.db curated category or tags: cli, developer-tools, go, testing. - [fake-gcs-server](https://www.automicvault.com/pkg/brew/fake-gcs-server/) - Shares av.db curated category or tags: cli, developer-tools, go, testing. - [gotests](https://www.automicvault.com/pkg/brew/gotests/) - Shares av.db curated category or tags: cli, developer-tools, go, testing. - [ali](https://www.automicvault.com/pkg/brew/ali/) - Local package facts share a topical domain. Shared terms: cli, developer, developer-tools, http, load. ## Combined YAML source View the package source record on GitHub. [combined/gor.yml](https://github.com/automic-vault/db/blob/main/combined/gor.yml) ## Sources - Nucleus package database - Geiger risk classifier - package-page enrichment - curated package history - package version freshness - av.db category and tag curation - package relationship graph - cross-ecosystem install command graph