macOS
Homebrewverified · 100%
brew install jsawklocal Homebrew formula metadata
brew / rank 9579
Install jsawk with Homebrew
Like awk, but for JSON, using JavaScript objects and arrays. Version 1.4 via Homebrew; verified from local package data.
install
Additional install commands
overview
Package summary
Like awk, but for JSON, using JavaScript objects and arrays
Project links
Commands and aliases
- jsawk
history
Project history and usage
jsawk is a small command-line filter that applies awk-like pipeline habits to JSON data by evaluating JavaScript over objects read from standard input.
Project history
The GitHub repository was created in May 2009. Its README frames the tool as awk for JSON: input is parsed into arrays and objects, JavaScript expressions filter or transform the data, and output returns to stdout for shell pipelines.
Adoption history
jsawk remained a compact Unix-style tool rather than a large ecosystem. Homebrew packages version 1.4 from the GitHub tag archive, and the repository has enough stars and forks to show durable interest among shell users who wanted JSON manipulation before jq became the default answer.
How it is used
Typical usage is piping REST API JSON into jsawk, selecting or transforming fields with JavaScript, and either emitting JSON again or printing custom text for another command in the pipeline.
Why package nerds care
jsawk is a useful historical waypoint in the JSON-on-the-command-line story: it shows the pre-jq period when developers tried to extend familiar text filters with JavaScript object access instead of adopting a purpose-built JSON query language.
Timeline
- 2009: GitHub repository created.
- 2010s: Homebrew packaged jsawk as a JSON-aware shell filter.
- 2026: Homebrew continued to package the 1.4 tag archive.
Related projects
- Related tools include awk, jq, gron, JSON.sh, fx, jc, and the author's resty command-line REST client.
Sources
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 bottle metadata was recorded.
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 |
|---|---|---|---|
jsawk | executable | indexed executable | Discovered from the local executable index. |
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-08-03
manager version1.4
manager updated
local dataunknown
upstreamnot available
latest detectednot detected
- okNo freshness warnings were generated.
install metadata
Package metadata
| Package key | brew:jsawk |
|---|---|
| Version | 1.4 |
| Package manager | Homebrew |
| Homepage | https://github.com/micha/jsawk |
| Repository | https://github.com/micha/jsawk |
| Bottle | not recorded |
| Service | none declared |
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.
Used sources
- Geiger risk classifier
- cross-ecosystem install command graph
- curated package history
- pkg.so package database
- pkgdb category and tag curation