Download

Both tools are single binaries for Linux, macOS and Windows, built and tested by GitHub Actions. The links always point to the latest release. Jump to jvq or jvqq.

jvq

Each archive below holds the jvq command with the license files and README. There’s nothing else to install apart from git, which jvq calls to check out the two commits.

System Download
Linux, x86-64 jvq_linux_amd64.tar.gz
Linux, ARM64 jvq_linux_arm64.tar.gz
macOS, Apple silicon jvq_darwin_arm64.tar.gz
macOS, Intel jvq_darwin_amd64.tar.gz
Windows, x86-64 jvq_windows_amd64.zip
Windows, ARM64 jvq_windows_arm64.zip

Checksums are in SHA256SUMS. Every release is listed on GitHub.

In GitHub Actions

You don’t need to download anything. The action fetches the right binary for the runner and checks its checksum:

- uses: actions/checkout@v7
  with:
    fetch-depth: 0
- uses: just-very-quickly/jvq@v0.9.0
  with:
    command: go test -run=^$ -bench=. -benchmem ./...

The quick start has the whole workflow file.

Install

On Linux or macOS:

tar -xzf jvq_linux_amd64.tar.gz
sudo mv jvq /usr/local/bin/
jvq version

The Linux binaries are statically linked and need no system libraries. The macOS ones aren’t signed by Apple, and macOS may ask you to allow them the first time. You can also clear the flag yourself:

xattr -d com.apple.quarantine jvq

On Windows, unzip the archive and run jvq.exe from a terminal.

With Go

go install github.com/just-very-quickly/jvq/cmd/jvq@latest

jvq uses only the Go standard library, so that’s the whole build.

How Releases Are Made

Every release is built by GitHub Actions from the release commit, after the full test suite has passed on Linux, macOS and Windows. The binaries are then smoke-tested on their own kind of machine: Linux on x86-64 and ARM, an Apple silicon Mac and Windows on x86-64. Each smoke test builds a small Go benchmark repository, checks that a change three times slower is caught and that a change to a comment passes. The Intel Mac and ARM Windows builds can’t run on those machines, so they’re checked for their architecture only. The commit is tagged and the release published only if every check passes.

jvqq

Each archive holds the jvqq command with the license files and README. It needs nothing else.

System Download
Linux, x86-64 jvqq_linux_amd64.tar.gz
Linux, ARM64 jvqq_linux_arm64.tar.gz
macOS, Apple silicon jvqq_darwin_arm64.tar.gz
macOS, Intel jvqq_darwin_amd64.tar.gz
Windows, x86-64 jvqq_windows_amd64.zip
Windows, ARM64 jvqq_windows_arm64.zip

Checksums are in SHA256SUMS. Every release is listed on GitHub.

Install

On Linux, x86-64, in one line:

curl -fsSL https://github.com/just-very-quickly/query/releases/latest/download/jvqq_linux_amd64.tar.gz | tar -xz jvqq
sudo mv jvqq /usr/local/bin/
jvqq --version

On a Mac, use jvqq_darwin_arm64.tar.gz or jvqq_darwin_amd64.tar.gz the same way. The macOS binaries aren’t signed by Apple, so macOS may ask you to allow them the first time, or you can run xattr -d com.apple.quarantine jvqq. On Windows, unzip the archive and run jvqq.exe from a terminal.

With Go

With Go 1.24 or later:

go install github.com/just-very-quickly/query/cmd/jvqq@latest

How Releases Are Made

Every release is built by GitHub Actions from the release commit, after the tests have passed on Linux, macOS and Windows, with the comparison against jq 1.7.1 on Linux and macOS. The binaries are then smoke-tested on their own kind of machine: Linux on x86-64 and ARM, an Apple silicon Mac and Windows on x86-64. Each check runs a select over 50,000 lines and looks for every line in order, reads a gzip file, counts with count_by, skips a broken line, and checks the exit codes. The Intel Mac and ARM Windows builds can’t run on those machines, so they’re checked for their architecture only. The commit is tagged and the release published only if every check passes.