Automic VaultAutomic Vault

brew

Install grok with Homebrew, MacPorts

DRY and RAD for regular expressions and then some. Version 0.9.2 via Homebrew; verified 2026-06-25.

install

Additional install commands

macOS

Homebrewverified · 100%
brew install grok

local Homebrew formula metadata

MacPortsverified · 94%
sudo port install grok

MacPorts ports tree · sysutils/grok/Portfile · source: api.github.com

overview

Package summary

DRY and RAD for regular expressions and then some

Commands and aliases

  • discogrok

history

Project history and usage

Jordan Sissel's grok is a small Unix-oriented log parsing tool that turns reusable regular-expression patterns into structured output.

Project history

The project predates its GitHub repository through the semicomplete.com and Google Code era referenced from the repository metadata. Its manual page describes the command as software for parsing logs, handling events, and turning unstructured text into structured data.

The C implementation builds a `grok` command, `discogrok`, and a shared library. Its pattern-file model lets users name regular expressions once and compose them in match blocks instead of repeating long PCRE expressions across log-processing configurations.

Adoption history

The standalone package remained a niche command-line tool, but the grok pattern idea became culturally important in log processing. Similar pattern syntax appears in widely used log pipelines and observability products, while the original package stayed available through package managers such as Homebrew and MacPorts.

How it is used

A typical invocation points `grok` at a configuration file with `-f`. Configurations declare inputs such as files or command output, define match blocks, and emit reactions such as the original line, captured fields, JSON, or shell-command input.

Why package nerds care

For package nerds, the appeal is the old-school Unix shape: a C command, PCRE-backed named patterns, installable pattern files, and log parsing without pulling in a larger log-ingestion stack.

Timeline

  • 2011: The GitHub repository was created and release tags from the 2011 series were published.
  • 2012: Homebrew and other package ecosystems carried the standalone tool during the early 2010s log-processing boom.
  • 2020s: The original project persisted as a niche packaged utility while grok-style patterns became common in larger logging systems.

Related projects

  • Related projects include Jordan Sissel's Ruby grok implementation, Logstash-style grok filters, and observability tools that use named pattern matching for unstructured logs.
  • It is also adjacent to traditional text-processing tools such as grep, awk, sed, and PCRE-based command-line filters.

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 10 platform targets.
  • Installs with 3 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

CommandKindExposureNote
discogrokcliglobal 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 version0.9.2
manager updated2026-06-25
local dataok
upstreamcurrent
latest detectedv0.9.2

https://github.com/jordansissel/grok

  • okNo freshness warnings were generated.

install metadata

Package metadata

Package keybrew:grok
Version0.9.2
Package managerHomebrew
Package manager pagehttps://formulae.brew.sh/formula/grok
Homepagehttps://github.com/jordansissel/grok
Repositoryhttps://github.com/jordansissel/grok
Upstream docshttps://github.com/jordansissel/grok#readme
LicenseBSD-2-Clause
Source archivehttps://github.com/jordansissel/grok/archive/refs/tags/v0.9.2.tar.gz
Last updated2026-06-25T13:37:44+02:00
Pulseupdated
Dependencieslibevent, pcre, tokyo-cabinet
Bottleavailable (on arm64_linux, arm64_monterey, arm64_sequoia, arm64_sonoma, arm64_tahoe, arm64_ventura, monterey, sonoma, ventura, x86_64_linux)
Homebrew post-installnot defined
Servicenone declared

registry facts

Source database details

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namegrok
Version Scheme0
Revision2
Head VersionHEAD
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedyes
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.

MacPorts95%

grok

sudo port install grok
  • normalized package name match
  • Matched by: Grok
MacPorts ports tree · api.github.com · MacPorts ports tree: sysutils/grok/Portfile from https://api.github.com/repos/macports/macports-ports/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