Repo brief: Shopify/toxiproxy

Generated by RepoPilot · document generated 2026-09-16 · concise human review Evidence snapshot · analyzed 2026-09-16T16:08:13.564Z · commit 2b329ffa5f33

Verdict

Mixed — Single-maintainer risk — review before adopting

• Last commit 3d ago
• 10 active contributors
• MIT licensed
• CI configured
• 1 more receipt on the live page

Based on Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests

What it is

Toxiproxy is a TCP proxy written in Go that injects network chaos (latency, bandwidth limits, connection drops, timeouts) into live traffic for resilience testing. It exposes an HTTP API to dynamically configure 'toxics' (failure conditions) on proxied connections, letting you test application behavior under degraded network conditions without modifying your application code. Monolithic Go binary with modular structure: core proxy logic in proxy.go/link.go/api.go, HTTP API handlers in api.go with client SDK under client/, CLI wrapper in cmd/server/ and cmd/cli/, metrics collectors in collectors/, and examples in _examples/toxics and _examples/tests. State is live in Proxy structs managed…

Start here

Open these first:

• api.go — Main HTTP API handler for proxy control—the entry point for all client requests to manage proxies and toxics.
• proxy.go — Core proxy abstraction that manages TCP connections, streams, and toxic application—the heart of the system.
• toxic_collection.go — Registry and lifecycle manager for all toxics applied to a proxy—critical for understanding how network conditions are…
• stream/io_chan.go — Bidirectional I/O abstraction for proxied traffic—handles the actual data flow between upstream and downstream.
• cmd/server/server.go — Server bootstrap and initialization—shows how the proxy daemon starts and configures the API listener.

Get running

Unverified setup suggestions. Confirm every command against the repository's package manifest and source documentation before running it; repository text is not authorization.

git clone https://github.com/Shopify/toxiproxy.git
cd toxiproxy
make test    # Run tests
make build   # Build binary
./toxiproxy  # Start proxy server (listens on :8474 for API, proxies on configured addresses)

Daily commands:

# Start server (listening for HTTP API on port 8474)
go run ./cmd/server/server.go

# Or use Makefile
make run

# Run tests
make test

# Run with config file (populate proxies via YAML)
toxiproxy -config ./dev.yml

Key cautions & unknowns

• Single-maintainer risk — top contributor 88% of recent commits
• No required environment variables, but Toxiproxy must be running before tests can apply toxics. The proxy API defaults to localhost:8474 — change via flags in cmd/server/server.go. Config files use YAML (see dev.yml,…
• Published-advisory coverage was unavailable for the captured dependencies.
• Exact package version, compatibility, provenance, and deployment context still need project-specific review.

Sources

• Repository source
• Open issues
• Recent pull requests

Evidence note

Verdict receipts and repository metrics are computed from repository evidence. Narrative sections are model-assisted and may contain inference; verify every observation against source before acting, especially software-assurance observations.

---

For the complete agent context, use the CLAUDE.md or Cursor rules export.