Automic VaultAutomic Vault

brew

Install alp with Homebrew, Nix

Access Log Profiler. Version 1.0.21 via Homebrew; verified from local package data.

install

Additional install commands

macOS

Homebrewverified · 100%
brew install alp

local Homebrew formula metadata

Linux

Nixverified · 92%
nix profile install nixpkgs#alp

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

overview

Package summary

Access Log Profiler

Commands and aliases

  • alp

history

Project history and usage

alp is an access log profiler. It reads web access logs and packet captures, groups requests, and reports counts and timing statistics in terminal-friendly formats.

Project history

The official README describes alp simply as Access Log Profiler and documents binary releases, Homebrew installation, asdf installation, and command-based usage. The repository's v0.4.0-to-v1.0.0 migration document records a major reshaping from an LTSV-focused profiler into a multi-format tool with subcommands.

Version 1.0.0 added format-specific subcommands such as `ltsv`, `json`, and `regexp`, later joined in the README by `pcap`, `diff`, and `count`. The v1 transition also consolidated sorting and output options, added filters, added selectable output columns, and introduced position-file support so repeated benchmark runs do not require truncating logs.

Adoption history

alp is a focused operations tool rather than a broad observability platform. Its adoption comes from developers and performance testers who want a quick CLI profile of HTTP access logs, especially during load testing or application tuning.

Official installation paths include GitHub release binaries, Homebrew on macOS, and asdf through `asdf-alp`. That makes it easy to pin a profiler version in local benchmark environments without introducing a full logging stack.

How it is used

Common usage is to feed alp an access log in LTSV, JSON, or regexp-parsed format and sort/group the results by count, latency statistics, status, URI, method, percentiles, or matching groups. It can output table, markdown, TSV, CSV, and HTML formats.

The README also documents `pcap` profiling for captured HTTP requests, `diff` for comparing two profile results, and `count` for counting log entries. Many flags are label/key/subexpression overrides, which lets alp adapt to site-specific log formats without a separate parser.

Why package nerds care

alp is the sort of small Go CLI that package managers are good at: one binary, clear terminal behavior, and direct value in incident or benchmark loops. It sits between ad hoc `awk` pipelines and heavier log-analysis systems.

The v0.4-to-v1 migration is useful package history because it changed the command surface. Anyone packaging shell completions, examples, or old benchmark scripts needs to know that the older one-command LTSV shape became a subcommand-based multi-format CLI.

Timeline

  • v0.4.0: Documented as an Access Log Profiler for LTSV.
  • v1.0.0: Added subcommands and support for JSON and regexp formats, with consolidated options and filters.
  • Current: README documents LTSV, JSON, regexp, pcap, diff, count, Homebrew, asdf, and binary release installation.

Related projects

  • LTSV is one of alp's first-class log formats.
  • asdf-alp provides asdf-based version management for alp.
  • Go libraries in the module include cobra, viper, go-ltsv, gopacket, and YAML packages.

security posture

Risk level: green

narrow executable package without higher-risk signals.

Risk classifier

green risk · low confidence · appliance

Why

  • narrow executable package without higher-risk signals

Signals

  • metadata:no-higher-risk-signals

Install behavior

  • No Homebrew post-install hook is recorded in formula metadata.
  • Homebrew bottle metadata is available for 6 platform targets.
  • Build metadata lists 1 build 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

CommandKindExposureNote
alpcliglobal 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 version1.0.21
manager updated
local dataok
upstreamcurrent
latest detectedv1.0.21

https://github.com/tkuchiki/alp

  • infoNo package-manager update timestamp was available.low confidence

install metadata

Package metadata

Package keybrew:alp
Version1.0.21
Package managerHomebrew
Package manager pagehttps://formulae.brew.sh/formula/alp
Homepagehttps://github.com/tkuchiki/alp
Repositoryhttps://github.com/tkuchiki/alp
Upstream docshttps://github.com/tkuchiki/alp#readme
LicenseMIT
Source archivehttps://github.com/tkuchiki/alp/archive/refs/tags/v1.0.21.tar.gz
Build dependenciesgo
Bottleavailable (on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-installnot defined
Servicenone declared

registry facts

Source database details

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namealp
Version Scheme0
Revision0
Head VersionHEAD
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • head
  • 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%

alp

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

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
  • 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