Automic VaultAutomic Vault

brew

Install jq-lsp with Homebrew, Nix

Jq language server. Version 0.1.17 via Homebrew; verified from local package data.

install

Additional install commands

macOS

Homebrewverified · 100%
brew install jq-lsp

local Homebrew formula metadata

Linux

Nixverified · 92%
nix profile install nixpkgs#jq-lsp

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

overview

Package summary

Jq language server

Commands and aliases

  • jq-lsp

history

Project history and usage

jq-lsp is Mattias Wadman's language server for jq, bringing editor features to jq filters and scripts. Its README lists syntax checking, missing function and binding diagnostics, goto definition, completion, import support, hover information, document symbols, and project-specific builtins through `.jq-lsp.jq`.

Project history

The project belongs to jq's later ecosystem rather than jq's original 2010s command-line history. It uses a modified version of itchyny's gojq parser and bases builtin documentation on jq manual data, making it a bridge between jq the CLI language and modern Language Server Protocol editor workflows.

Public release artifacts began with the 0.1 series. The November 2025 releases added IntelliJ/LSP4IJ support, import-search behavior, jq 1.8 builtins and docs, parser fixes, and packaged binaries. January and February 2026 releases refined server internals and parser traversal.

Adoption history

jq-lsp is surfaced through editor integrations rather than as a standalone end-user data tool. The README points users toward vscode-jq, Neovim lspconfig and mason.nvim, Emacs lsp-mode, Helix, and IntelliJ with LSP4IJ, matching how language servers are usually adopted.

How it is used

Developers install `jq-lsp` with Go or a package manager and let an editor launch it for `.jq` files. The `.jq-lsp.jq` file lets a project declare additional builtin functions or variables so diagnostics and completion match the environment where jq code actually runs.

Why package nerds care

jq-lsp is package-nerd notable because it turns jq from a terse shell pipeline language into something editors can understand. It also shows a common LSP pattern: reuse an existing language parser, ship one small server binary, and let many editors share the same intelligence.

Timeline

  • 2025-11-18: v0.1.2 and v0.1.14 release artifacts were published in the 0.1 line.
  • 2025-11-18: v0.1.14 added IntelliJ with LSP4IJ support, jq 1.8 builtins and docs, import search-path support, and related parser fixes.
  • 2025-11-27: v0.1.15 fixed parsing of binary operators with binding.
  • 2026-01-01: v0.1.16 updated gojq, moved more server CLI behavior into jq, and fixed position handling.
  • 2026-02-12: v0.1.17 corrected suffix-list traversal.

Related projects

  • Related projects include jq, gojq, vscode-jq, Neovim lspconfig, mason.nvim, Emacs lsp-mode, Helix, and IntelliJ LSP4IJ.

security posture

Risk level: blue

broad file, network, media, or database tool signal.

Risk classifier

blue risk · medium confidence · tool

Why

  • broad file, network, media, or database tool signal

Signals

  • text:server

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.

local files

Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.

Configuration files

Config paths the tool may read or write during local use.

Unix
.jq-lsp.jq

executables

Installed executables

CommandKindExposureNote
jq-lspcliglobal 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.1.17
manager updated
local dataok
upstreamcurrent
latest detectedv0.1.17

https://github.com/wader/jq-lsp

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

install metadata

Package metadata

Package keybrew:jq-lsp
Version0.1.17
Package managerHomebrew
Package manager pagehttps://formulae.brew.sh/formula/jq-lsp
Homepagehttps://github.com/wader/jq-lsp
Repositoryhttps://github.com/wader/jq-lsp
Upstream docshttps://github.com/wader/jq-lsp#readme
LicenseMIT
Source archivehttps://github.com/wader/jq-lsp/archive/refs/tags/v0.1.17.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 Namejq-lsp
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%

jq-lsp

nix profile install nixpkgs#jq-lsp
  • normalized package name match
  • Matched by: Jq Lsp
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/jq/jq-lsp/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 configuration and credential file locations
  • curated package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment