Automic VaultAutomic Vault

brew

jq-lsp mit Homebrew, Nix installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für jq-lsp in AI-Agent-Workflows.

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install jq-lsp

local Homebrew formula metadata

Linux

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

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

Überblick

Paketzusammenfassung

Jq language server

Befehle und Aliase

  • jq-lsp

Verlauf

Projektgeschichte und Nutzung

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`.

Projektgeschichte

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.

Adoptionsgeschichte

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.

Wie es verwendet wird

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.

Warum Paket-Nerds sich dafür interessieren

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.

Zeitleiste

  • 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.

Sicherheitslage

Risikostufe: blue

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

Risikoklassifikator

blue Risiko · mittel Konfidenz · tool

Warum

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

Signale

  • text:server

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Homebrew-Bottle-Metadaten sind für 6 Plattformziele verfügbar.
  • Build-Metadaten listen 1 Build-Abhängigkeiten.

Empfohlene Prüfung

Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.

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

Installierte Executables

BefehlArtSichtbarkeitHinweis
jq-lspcliglobales Executable

Aktualität

Version und Aktualität

Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.

Seite generiert2026-07-25
Manager-Version0.1.18
Manager aktualisiert2026-07-20
lokale DatenOK
Upstreamaktuell
neueste erkannte Versionv0.1.18

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

  • OKEs wurden keine Aktualitätswarnungen generiert.

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:jq-lsp
Version0.1.18
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/jq-lsp
Homepagehttps://github.com/wader/jq-lsp
Repositoryhttps://github.com/wader/jq-lsp
Upstream-Dokumentationhttps://github.com/wader/jq-lsp#readme
LizenzMIT
Quellarchivhttps://github.com/wader/jq-lsp/archive/refs/tags/v0.1.18.tar.gz
Zuletzt aktualisiert2026-07-20T12:44:27Z
Pulseupdated
Build-Abhängigkeitengo
Bottleverfügbar (auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

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-Datenbank-Treffer

Andere Paketmanager-Einträge

Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.

Nix95%

jq-lsp

nix profile install nixpkgs#jq-lsp
  • normalized package name match
  • Abgeglichen nach: 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

Quellspur

Aus Repository-Daten generiert

Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.

Verwendete Quellen

  • 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