# Install libtrace with Homebrew, Nix

Library for trace processing supporting multiple inputs. Version 4.0.34 via Homebrew; verified from local package data. Also installable with nix: nix profile install nixpkgs#libtrace.

## Install

```sh
sudo av install brew:libtrace
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install libtrace
```

  Evidence: local Homebrew formula metadata

### Linux

- Nix (92%):

```sh
nix profile install nixpkgs#libtrace
```

  Evidence: nixpkgs package indexes: pkgs/by-name/li/libtrace/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

## Package facts

- **Package key:** brew:libtrace
- **Package manager:** Homebrew
- **Version:** 4.0.34
- **Source summary:** Library for trace processing supporting multiple inputs
- **Homepage:** <https://github.com/LibtraceTeam/libtrace>
- **Repository:** <https://github.com/LibtraceTeam/libtrace>
- **Generated:** 2026-08-03T19:37:03+00:00

## Executables

- traceconvert (alias)
- tracediff (alias)
- traceends (alias)
- tracefilter (alias)
- tracemcast (alias)
- tracemerge (alias)
- tracepktdump (alias)
- tracereplay (alias)
- tracereport (alias)
- tracertstats (alias)
- tracesplit (alias)
- tracesplit_dir (alias)
- tracestats (alias)
- tracesummary (alias)
- tracetop (alias)
- tracetopends (alias)
- traceucast (alias)

## Install behavior

- Bottle: not available

## Freshness

- Page generated: 2026-08-03
- Package-manager version: 4.0.34
## Project history and usage

libtrace is a C library and suite of trace tools for processing live and offline network packet captures across multiple trace and interface formats.

### Project history

The libtrace README states that the code was originally developed by the University of Waikato WAND research group and was primarily designed for the real-time interface to the Waikato DAG Capture Point software. It later grew beyond that original environment to support a range of trace and interface formats.

The repository records copyright for University of Waikato code through 2022 and for later code and documentation contributed by Shane Alcock from 2023 through 2026. The 4.0 series introduced a parallel packet-processing API for multithreaded workloads.

### Adoption history

libtrace's adoption is strongest in network measurement, packet-trace analysis, and research tooling rather than broad desktop use. Its command-line utilities, including traceconvert, tracefilter, tracemerge, tracereport, tracesplit, tracestats, and tracesummary, made it useful as both a library and a practical trace-processing toolkit.

### How it is used

Users employ libtrace to read, filter, convert, replay, summarize, and report on traffic captures from offline files or live interfaces. Developers link against the library when they need one API over multiple capture formats and, in the 4.0 line, when they need parallel packet processing.

### Why package nerds care

For packet-analysis package nerds, libtrace is interesting because it is not just another pcap wrapper: it comes from a university measurement environment, carries a family of trace* command-line tools, and preserves support for specialized capture systems alongside common packet formats.

### Timeline

- 2007-2022: University of Waikato copyright range shown in the README for code through version 4.0.20.
- 2017: GitHub releases page lists libtrace 4.0.2 as a public 4.0-series release.
- 2023: README records Shane Alcock copyright for newer code and documentation beginning in 2023.
- 2026: GitHub releases page lists Libtrace 4.0.33 on June 10, 2026.

### Related projects

- Waikato DAG Capture Point software is the original environment named by the README.
- libpacketdump, wandio, libwandder, and related LibtraceTeam repositories sit in the same packet-trace tooling ecosystem.
- pcap-oriented tools such as tcpdump and Wireshark are adjacent consumers or producers of traffic capture data, though libtrace focuses on programmatic trace processing.

### Sources

- <http://www.wand.net.nz/>
- <https://github.com/LibtraceTeam/libtrace>
- <https://github.com/LibtraceTeam/libtrace/releases>
- <https://github.com/LibtraceTeam/libtrace/wiki/ChangeLog>


## Security Notes

library-like package without higher-risk signals.

- **Geiger risk:** green / low
- library-like package without higher-risk signals

## Other Package-Manager Records

- Nix - libtrace: normalized package name match | nixpkgs package indexes: pkgs/by-name/li/libtrace/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1


## Combined YAML source

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


## Sources

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