HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
jqlang
jq
C2012–2026
jqlang / jq

jq

Command-line JSON processor

79Distinct people
104Mentions
2Explicit recommenders
36.1KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Command-line JSON processor

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

I highly recommend anyone to look at jq's VM implementation some time, it's kind of mind-blowing how it works under the hood:…

bouk used a recommendation phrase. 2 indexed comments match. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 4:59:52 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year104 dated mentions

Observed mentions: 2012-10-21 17:50:32 UTC to 2026-03-29 02:02:20 UTC.

05101520252012-01-01 00:00:00 UTC to 2013-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20122013-01-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 12 mentions; 0 submissions, 12 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 7 mentions; 0 submissions, 7 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 9 mentions; 0 submissions, 9 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 8 mentions; 3 submissions, 5 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 14 mentions; 3 submissions, 11 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 25 mentions; 5 submissions, 20 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 11 mentions; 0 submissions, 11 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 8 mentions; 2 submissions, 6 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20122012-01-01 00:00:00 UTC2013-01-01 00:00:00 UTC101
20132013-01-01 00:00:00 UTC2014-01-01 00:00:00 UTC202
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC000
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC211
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC211
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC101
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC12012
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC707
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC909
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC835
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC14311
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC25520
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC11011
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC826
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC202

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
jq jq is a lightweight and flexible command-line JSON processor akin to sed,awk,grep, and friends for JSON data. It's written in portable C and has zero runtime dependencies, allowing you to easily slice, filter, map, and transform structured data. Documentation Official Documentation: jqlang.org Try jq Online: play.jqlang.org Installation Prebuilt Binaries Download the latest releases from the GitHub release page. The platform-specific assets are standalone executables, not archives. On macOS and Linux, rename the downloaded file to jq and make it executable with chmod +x jq. Docker Image Pull the jq image to start quickly with Docker. Run with Docker Example: Extracting the version from a package.json file docker run --rm -i ghcr.io/jqlang/jq:latest < package.json '.version' Example: Extracting the version from a package.json file with a mounted volume docker run --rm -i -v "$PWD:$PWD" -w "$PWD" ghcr.io/jqlang/jq:latest '.version' package.json Building from source Dependencies libtool make automake autoconf Instructions git submodule update --init # if building from git to get oniguruma autoreconf -i # if building from git ./configure --with-oniguruma=builtin make clean # if upgrading from a version previously built from source make -j8 make check sudo make install sudo ldconfig # on Linux, if jq cannot find libjq.so Build a statically linked version: make clean make LDFLAGS=-all-static If you're not using the latest git version but instead building a released tarball (available on the release page), skip the autoreconf step, and flex or bison won't be needed. Cross-Compilation For details on cross-compilation, check out the GitHub Actions file and the cross-compilation wiki page. Community & Support Questions & Help: Stack Overflow (jq tag) Chat & Community: Join us on Discord Wiki & Advanced Topics: Explore the Wiki License jq is released under the MIT License. jq's documentation is licensed under the Creative Commons CC BY 3.0. jq uses parts of the open source C library "decNumber", which is distributed under ICU License
Read the full README on GitHub

What Hacker News says

14 sources
Repo author here, let me promote jq a bit – it's much more than a simple command-line JSON processor you know it for: * It is a generator-based language which means you operate streams of values rather than single values. Takes some time to get used to, but you'd never want to go back to traditional model, at least for data processing. See 'Generators and iterators' section of the man page: https://github.com/stedolan/jq/blob/cff5336ec71b6fee396a95bb... * Designed for CLI, it makes it easy and even pushes you to express your program as a single pipeline. You rarely need variables, functions or any control structure. And pipelines are great to build iteratively, debug and compose (see https://jqplay.org, https://jqterm.com) * Core language is small but powerful with features like slicing, destructuring, complex assignments and error handli
Read the rest
ng. And you are already an expert in it's (immutable) data structures – it is just JSON * Batteries included in the stdlib – regex, path operations, C math/dates, algorithms. Modules are supported, but I did not need any dependencies for solving Advent of Code. * jq is ubiquitous. Often pre-installed, tiny binary, no dependencies, basically single version (ok, awk is better – anything else?) Being a go-to tool for JSON is sort of a double-edged sword – people just don't look past that. But nowadays JSON is the format for data, everything is convertible to it. And you can feed plain text into jq using --raw-input flag. i.e.: jq -nR '[inputs]' /etc/hosts The main limitation is there is no I/O whatsoever – you can't read from file/network/pipe/system from the program. You need to provide all inputs upfront. Hope that explains why I prefer jq. For any programming really, not just AOC
In Solving Advent of Code with jq
If there's no planned changes or unreleased work in the repo, then there's not much need for more releases. Jq is a pretty small tool and isn't obviously incomplete. Though it's funny because I do agree that in the past that jq wasn't having its committed code being released often enough. There was a popular Github issue[1] with arguments and 70+ reactions about a confusing feature in jq that turned out to have already been fixed and committed in 2015, before the Github issue was even opened, but the fix didn't actually make it into a released version until 2018. Definitely one of the more frustrating cases of investigating a software issue I ran into. Everyone should make sure their project's release process can promptly release updates! [1] https://github.com/stedolan/jq/issues/1110
In Jq Internals: Backtracking (2017)
So - veteran data wrangler here. I skimmed some of Humana's files. There's lots of repetition that can easily be removed when converting from a raw input to an analytical dataset - basically the huge blocks of text in "BILL_TYPE_CODE: 130,139,..." in the ADDITIONAL_INFO field can be normalized away by building a quasi-Huffman-encoded lookup table. Noteworthy(?): there seems to be a limit of ~100~ 140 sets of prices, as seen in the filenames: 2022-08-25_NNN_in-network-rates_0000000XXXXX.csv.gz ~Did I miss something? ... or is this some kind of technical limitation for Humana?~ Edit: I missed the alphabetical ordering. Still, only about 140 price sets. Also, each plan member's JSON file has a small chunk of useful information, then a useless list of all 15k gz parts of a relevant NN_in-network-rates file (you only need the first filename
Read the rest
to figure out which NN to reference). For these files, you can use Range requests to download only the first, say, 50KB, and pipe it to gunzip and jq. (https://github.com/stedolan/jq/issues/31#issuecomment-900184...) I would also be interested in helping throw such an analytical dataset into BigQuery. It'll be great for sharing an open dataset. No doubt this will still be a gigantic headache, but it is tractable.
In Health insurers just published close to a trillion hospital prices
I completely agree when your goal is GSD just use the tools you have. When you have time to sharpen the saw come back and dig into the details of how jq and tools like it work and where their limits are. Looking at the jq builtins[1] can be very enlightening If you get to the point where your goal is to increase your jq skills I'd recommend looking at the jq questions on Stack Overflow and posting your own solution. Contributing a solution to https://rosettacode.org/wiki/Category:Jq is also good. 1- https://github.com/stedolan/jq/blob/master/src/builtin.jq
In Zq: An easier and faster alternative to jq
Since no one seems to know about it, jq is described in great detail on the github wiki page [0]. That flattens the learning curve a lot. It's not as arcane as it seems. The touted claim that is fundamentally stateless is not true. jq is also stateful in the sense that it has variables. If you want, you can write regular procedural code this way. Some examples [1] The real problem of jq is that it is currently lacking a maintainer to assess a number of PRs that have accumulated since 2018. [0] https://github.com/stedolan/jq/wiki/jq-Language-Description [1] https://github.com/fadado/JBOL/blob/master/fadado.github.io/...
In Zq: An easier and faster alternative to jq
In today's world of excellent CLI tools I don't think grep is a good choice, especially for checking irregular languages like XML. [0] I use tools like `jq` [1] or `yq` [2] all the time for CI checks. One useful check, is we have a configuration file stored as several hundred lines of YAML. Its a nice thing to maintain a sorted order for that, so we have a git pre-commit hook that runs the following: > yq eval --inplace '.my_key|= sort' my_file.yaml Of course, a pre-commit hook or CI both work. There's pros and cons of both. For our team, the pre-commit hook is a low enough level of effort, and doesn't require a CI check for something that executes in milliseconds. [0] https://stackoverflow.com/a/1732454 [1] https://github.com/stedolan/jq [2] https://github.com/mikefarah/yq
In Grep one-liners as CI tasks

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.