pkg.soopen package index

brew / rank 4659

Install toxiproxy with Homebrew, dnf, MacPorts, Nix

TCP proxy to simulate network & system conditions for chaos & resiliency testing. Version 2.12.0 via Homebrew; verified 2026-07-26. Also installable with nix: nix profile install nixpkgs#toxiproxy.

Install commandSecurity notes

install

Additional install commands

macOS

Homebrewverified · 100%
brew install toxiproxy

local Homebrew formula metadata

MacPortsverified · 94%
sudo port install toxiproxy

MacPorts ports tree · net/toxiproxy/Portfile · source: api.github.com

Linux

Fedora dnfverified · 92%
sudo dnf install toxiproxy

Fedora Rawhide package metadata · toxiproxy · source: dl.fedoraproject.org

Nixverified · 92%
nix profile install nixpkgs#toxiproxy

nixpkgs package indexes · pkgs/by-name/to/toxiproxy/package.nix · source: api.github.com

overview

Package summary

TCP proxy to simulate network & system conditions for chaos & resiliency testing

Commands and aliases

  • toxiproxy-cli
  • toxiproxy-server

history

Project history and usage

Toxiproxy is Shopify's TCP proxy for simulating network conditions in tests, CI, and development. It lets applications route connections through a local proxy and then apply deterministic or randomized failures such as latency, bandwidth limits, timeouts, packet loss, resets, and disabled links.

Project history

Shopify created Toxiproxy during its 2014 resiliency work, when the infrastructure team needed automated ways to test behavior under slow or unavailable dependencies before the holiday traffic season. The official README says Shopify had been using it in all development and test environments since October 2014.

The first public GitHub release, v1.0.0, was published in January 2015 as 'Public Release'. The project later moved through a 2.x line with a Go TCP proxy server, HTTP API, command-line client, metrics documentation, and multiple client libraries.

Adoption history

Toxiproxy spread because it packaged a distributed-systems testing trick into a repeatable developer tool. Instead of requiring root-only Linux networking tools such as tc or iptables, developers could install a user-space proxy, declare upstream services, and manipulate faults from tests through HTTP or client libraries.

The official README lists clients for Ruby, Go, Python, .NET, PHP, Node.js, Java, Haskell, Rust, and Elixir. Homebrew, MacPorts, Nix, and Fedora packaging in the source facts show it being distributed as a standalone CLI/server tool rather than just as a Ruby testing helper.

How it is used

A typical test setup starts `toxiproxy-server`, populates proxy definitions for dependencies such as Redis or MySQL, points the application at the proxy listen ports, and uses a client or `toxiproxy-cli` to apply toxics around a test case.

The README's Rails example demonstrates taking down Redis or adding latency to MySQL to verify fallback behavior. The same model applies to any TCP dependency, which is why Toxiproxy fits CI and local development better than manually editing host networking rules.

Why package nerds care

For package nerds, Toxiproxy is a high-signal example of infrastructure testing becoming a simple package install. It turns failure injection into `brew install toxiproxy`, a server process, and a CLI/API surface that can be scripted from test suites.

It also helped normalize resilience testing in ordinary application repositories: package maintainers and application developers could add fault-injection checks without privileged networking setup or specialized chaos-testing platforms.

Timeline

  • 2014: Shopify begins using Toxiproxy in development and test environments.
  • 2015: v1.0.0 'Public Release' published on GitHub Releases.
  • 2.x: README documents cross-platform binaries, Docker/GitHub container registry usage, HTTP API, metrics, toxics, and multiple language clients.

Related projects

  • The README positions Toxiproxy as a safer test/CI alternative to nc, tc, iptables, and similar low-level networking tools. Shopify engineering articles also connect it to resiliency work and circuit-breaker testing.

security posture

Risk level: orange

broad file, network, media, or database tool signal. formula declares a Homebrew service.

Risk classifier

orange risk · medium confidence · infrastructure

Why

  • broad file, network, media, or database tool signal
  • formula declares a Homebrew service

Signals

  • metadata:service
  • text:network,server

Install behavior

  • No Homebrew bottle metadata was recorded.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to 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
config/toxiproxy.json

executables

Installed executables

CommandKindExposureNote
toxiproxy-cliexecutableindexed executableDiscovered from the local executable index.
toxiproxy-serverexecutableindexed executableDiscovered from the local executable index.

freshness

Version and freshness

These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.

page generated2026-08-03
manager version2.12.0
manager updated2026-07-26
local dataunknown
upstreamnot available
latest detectednot detected
  • okNo freshness warnings were generated.

install metadata

Package metadata

Package keybrew:toxiproxy
Version2.12.0
Package managerHomebrew
Homepagehttps://github.com/shopify/toxiproxy
Repositoryhttps://github.com/Shopify/toxiproxy
Last updated2026-07-26T00:51:26+02:00
Pulseupdated
Bottlenot recorded
Servicenone declared

source database matches

Other package-manager records

Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.

Nix95%

toxiproxy

nix profile install nixpkgs#toxiproxy
  • normalized package name match
  • Matched by: Toxiproxy
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/to/toxiproxy/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
dnf95%

toxiproxy 2.1.4-23.fc44

TCP proxy to simulate network and system conditions for resiliency testing

https://github.com/Shopify/toxiproxy

sudo dnf install toxiproxy
  • License: MIT
  • Category: Unspecified
  • Architecture: x86_64
  • Source Package: golang-github-shopify-toxiproxy
  • 6 dependencies
  • 2 provides
  • normalized package name match
  • Matched by: Toxiproxy
Fedora Rawhide package metadata · dl.fedoraproject.org · Fedora Rawhide package metadata: toxiproxy from https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything/x86_64/os/repodata/07190dc5ae9f35ae73866675fed6d95fe6e8d9fe22c9d7cdf85862cb2ed24a4c-primary.xml.zst
MacPorts95%

toxiproxy

sudo port install toxiproxy
  • normalized package name match
  • Matched by: Toxiproxy
MacPorts ports tree · api.github.com · MacPorts ports tree: net/toxiproxy/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1

package graph

Links come from deterministic package relationships, av.db category and tag curation, ecosystem matches, and package hub membership.

source trail

Generated from repository data

This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.

Used sources

  • Geiger risk classifier
  • cross-ecosystem install command graph
  • curated configuration and credential file locations
  • curated package history
  • external package-manager database matches
  • pkg.so package database
  • pkgdb category and tag curation