install

Additional install commands

macOS

Homebrewverified · 100%

brew install zipkin

local Homebrew formula metadata

Linux

Nixverified · 92%

nix profile install nixpkgs#zipkin

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

overview

Package summary

Collect and visualize traces written in Zipkin format

Project links

Commands and aliases

zipkin

history

Project history and usage

Zipkin is a distributed tracing system born inside Twitter and later stewarded by the OpenZipkin volunteer organization. For package users it is the classic lightweight trace collector and UI: run a server, point instrumented services at it, and inspect latency paths through a service graph.

Project history

Twitter announced Zipkin as open source on 7 June 2012, describing it as a system created to gather timing data for requests moving through the services behind the Twitter API. The announcement says Zipkin began during Twitter's first Hack Week as a basic implementation of the Google Dapper paper for Thrift, then grew to support tracing HTTP, Thrift, Memcache, SQL, and Redis requests.

OpenZipkin later became the project home. The official community page says Zipkin was originally created by Twitter and is now run by the OpenZipkin volunteer organization, which stewards code, docs, specs, and support.

The server evolved into a standalone Java service with collectors, storage options, a query/UI layer, and instrumentation integrations. The current README and site describe support for HTTP or Kafka reporting, alternatives such as ActiveMQ, gRPC, RabbitMQ, and Pulsar, and storage backends including in-memory, Cassandra, and Elasticsearch.

Adoption history

Zipkin's initial adoption came from Twitter's own production need to understand latency in a service-oriented architecture. The 2012 announcement says it helped find optimizations such as removing memcache requests, rewriting slow MySQL SELECTs, and fixing service timeouts.

After open sourcing, Zipkin became one of the default names in distributed tracing alongside systems such as Dapper-inspired internal tools and later Jaeger. Its adoption was helped by a simple local demo path, a web UI, many instrumentation libraries, and a data model that other systems could emit.

The OpenZipkin community page describes a volunteer-run project with GitHub repositories, a website, mailing list, chat, support channels, and community events. That community model is part of why Zipkin remained packageable after its Twitter-origin architecture changed hands.

How it is used

A typical user runs the Zipkin server, instruments applications with a tracer or instrumentation library, sends spans to Zipkin, and queries traces by service, operation, tags, duration, or trace ID. The UI shows trace waterfalls and a dependency diagram for aggregate service relationships.

For local or package-manager use, the README documents running the server as a jar, Docker container, or installed command, then opening the UI on the Zipkin endpoint. In production, users choose collectors and storage backends according to the traffic and retention requirements of their service architecture.

Why package nerds care

Zipkin is important in package catalogs because it makes distributed tracing something a developer can install and run locally, not only a hosted observability product. That has made it useful for demos, integration tests, platform teams, and service owners validating instrumentation.

It also occupies a historical bridge between the Dapper paper era and the broader observability ecosystem. The package is a runnable artifact of how tracing moved from large-company infrastructure into everyday open-source service stacks.

Timeline

2012: Twitter open sources Zipkin after its Hack Week origin and production use.
2013: Twitter publishes a browser-extension workflow showing continued work to make traces easier to consume.
2010s: OpenZipkin becomes the volunteer organization stewarding Zipkin code, docs, specs, and support.
2020s: Zipkin continues as a standalone server with multiple transports, storage backends, UI, and instrumentation integrations.

Related projects

Google Dapper, the tracing paper that inspired Zipkin's original design.
Twitter Finagle, Scrooge, Scribe, Cassandra, ZooKeeper, Bootstrap, and D3, named by Twitter as early Zipkin dependencies or surrounding infrastructure.
Jaeger, OpenTelemetry, Brave instrumentation, service meshes, and other distributed tracing systems that interoperate with or sit near Zipkin in observability stacks.

Sources

security posture

Risk level: orange

formula declares a Homebrew service.

Risk classifier

orange risk · medium confidence · infrastructure

Why

formula declares a Homebrew service

Signals

metadata:service

Install behavior

No Homebrew post-install hook is recorded in formula metadata.
Formula metadata declares a service or daemon block.
Homebrew bottle metadata is available for 1 platform targets.
Installs with 1 runtime dependencies.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.

executables

Installed executables

Command	Kind	Exposure	Note
`zipkin`	cli	global executable

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-07-08

manager version3.6.1

manager updated

local dataok

upstreamnot checked

latest detectednot detected

https://zipkin.io

infoNo package-manager update timestamp was available.low confidence
infoRelease/tag comparison is only available for GitHub repositories.https://zipkin.ionone confidence

install metadata

Package metadata

Package key	brew:zipkin
Version	3.6.1
Package manager	Homebrew
Package manager page	https://formulae.brew.sh/formula/zipkin
Homepage	https://zipkin.io
Repository	https://github.com/openzipkin/zipkin
Upstream docs	https://zipkin.io/pages/existing_instrumentations
License	Apache-2.0
Source archive	https://search.maven.org/remotecontent?filepath=io/zipkin/zipkin-server/3.6.1/zipkin-server-3.6.1-exec.jar
Dependencies	openjdk
Bottle	available (on all)
Homebrew post-install	not defined
Service	declared

registry facts

Source database details

Source Database	Homebrew formula API
Tap	homebrew/core
Full Name	zipkin
Version Scheme	0
Revision	0
Bottle Stable Root URL	https://ghcr.io/v2/homebrew/core
Deprecated	no
Disabled	no
Keg Only	no
URL Keys	stable

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%

zipkin

nix profile install nixpkgs#zipkin

normalized package name match
Matched by: Zipkin

nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/zi/zipkin/package.nix from https://api.github.com/repos/NixOS/nixpkgs/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.

Combined YAML source

View the package source record on GitHub.

combined/zipkin.yml

Used sources

Geiger risk classifier
Nucleus package database
av.db category and tag curation
cross-ecosystem install command graph
curated package history
external package-manager database matches
package relationship graph
package version freshness
package-page enrichment

Install zipkin with Homebrew, Nix