
Security News
The Next Open Source Security Race: Triage at Machine Speed
Claude Opus 4.6 has uncovered more than 500 open source vulnerabilities, raising new considerations for disclosure, triage, and patching at scale.
libpg-query
Advanced tools
This is the official PostgreSQL parser, compiled to WebAssembly (WASM) for seamless, cross-platform compatibility. Use it in Node.js or the browser, on Linux, Windows, or anywhere JavaScript runs.
Built to power pgsql-parser, this library delivers full fidelity with the Postgres C codebase — no rewrites, no shortcuts.
🎯 Want to parse + deparse (full round trip)?
We highly recommend usingpgsql-parserwhich leverages a pure TypeScript deparser that has been battle-tested against 23,000+ SQL statements and is built on top of libpg-query.
npm install libpg-query
import { parse } from 'libpg-query';
const result = await parse('SELECT * FROM users WHERE active = true');
// {"version":170004,"stmts":[{"stmt":{"SelectStmt":{"targetList":[{"ResTarget" ... "op":"SETOP_NONE"}}}]}
Our latest is built with 17-latest branch from libpg_query
| PG Major Version | libpg_query | npm dist-tag |
|---|---|---|
| 17 | 17-6.1.0 | pg17 |
| 16 | 16-5.2.0 | pg16 |
| 15 | 15-4.2.4 | pg15 |
| 14 | 14-3.0.0 | pg14 |
| 13 | 13-2.2.0 | pg13 |
parse(query: string): Promise<ParseResult>Parses the SQL and returns a Promise for the parse tree. May reject with a parse error.
import { parse } from 'libpg-query';
const result = await parse('SELECT * FROM users WHERE active = true');
// Returns: ParseResult - parsed query object
parseSync(query: string): ParseResultSynchronous version that returns the parse tree directly. May throw a parse error.
import { parseSync } from 'libpg-query';
const result = parseSync('SELECT * FROM users WHERE active = true');
// Returns: ParseResult - parsed query object
⚠ Note: If you need additional functionality like fingerprint, scan, deparse, or normalize, check out the full package (@libpg-query/parser) in the ./full folder of the repo.
The library provides both async and sync methods. Async methods handle initialization automatically, while sync methods require explicit initialization.
Async methods handle initialization automatically and are always safe to use:
import { parse } from 'libpg-query';
// These handle initialization automatically
const result = await parse('SELECT * FROM users');
Sync methods require explicit initialization using loadModule():
import { loadModule, parseSync } from 'libpg-query';
// Initialize first
await loadModule();
// Now safe to use sync methods
const result = parseSync('SELECT * FROM users');
loadModule(): Promise<void>Explicitly initializes the WASM module. Required before using any sync methods.
import { loadModule, parseSync } from 'libpg-query';
// Initialize before using sync methods
await loadModule();
const result = parseSync('SELECT * FROM users');
Note: We recommend using async methods as they handle initialization automatically. Use sync methods only when necessary, and always call loadModule() first.
interface ParseResult {
version: number;
stmts: Statement[];
}
interface Statement {
stmt_type: string;
stmt_len: number;
stmt_location: number;
query: string;
}
Note: The return value is an array, as multiple queries may be provided in a single string (semicolon-delimited, as PostgreSQL expects).
This package uses a WASM-only build system for true cross-platform compatibility without native compilation dependencies.
Install dependencies:
pnpm install
Build WASM artifacts:
pnpm run build
Clean WASM build (if needed):
pnpm run clean
Rebuild WASM artifacts from scratch:
pnpm run clean && pnpm run build
The WASM build process:
wasm/libpg-query.js and wasm/libpg-query.wasm filespnpm run test
pnpm run clean && pnpm run build && pnpm run test
"fetch failed" errors during tests:
pnpm run clean && pnpm run build"WASM module not initialized" errors:
Build environment issues:
The build process generates these files:
wasm/libpg-query.js - Emscripten-generated JavaScript loaderwasm/libpg-query.wasm - WebAssembly binarywasm/index.js - ES module exportswasm/index.cjs - CommonJS exports with sync wrappersBuilt on the excellent work of several contributors:
🛠 Built by the Constructive team — creators of modular Postgres tooling for secure, composable backends. If you like our work, contribute on GitHub.
pgsql-parser.pgsql-parser for parsing and deparsing SQL queries.AS DESCRIBED IN THE LICENSES, THE SOFTWARE IS PROVIDED "AS IS", AT YOUR OWN RISK, AND WITHOUT WARRANTIES OF ANY KIND.
No developer or entity involved in creating Software will be liable for any claims or damages whatsoever associated with your use, inability to use, or your interaction with other users of the Software code or Software CLI, including any direct, indirect, incidental, special, exemplary, punitive or consequential damages, or loss of profits, cryptocurrencies, tokens, or anything else of value.
FAQs
The real PostgreSQL query parser
The npm package libpg-query receives a total of 102,779 weekly downloads. As such, libpg-query popularity was classified as popular.
We found that libpg-query demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
Claude Opus 4.6 has uncovered more than 500 open source vulnerabilities, raising new considerations for disclosure, triage, and patching at scale.

Research
/Security News
Malicious dYdX client packages were published to npm and PyPI after a maintainer compromise, enabling wallet credential theft and remote code execution.

Security News
gem.coop is testing registry-level dependency cooldowns to limit exposure during the brief window when malicious gems are most likely to spread.