pg-lock-xray@0.1.1
VERIFIED· startup onlyPublisher claims: "Enables scanning PostgreSQL migrations for ACCESS EXCLUSIVE lock hazards and rewriting unsafe SQL into zero-downtime forms via the rewrite_zero_downtime MCP tool." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Startup only; authenticated tool behavior not tested.- Tested
- server startup over stdio (initialize sent) · every file read, file written and host contacted by what ran
- Not tested
- the tool list (the server exited before answering) · what the tools do when called with real credentials
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
- no credential variables read in the code
- Where it talks to
- no vendor host named in the code
- What the honeypot saw
- no credential files read · no network
- What we could not test
- the tool list (the server exited before answering) · what the tools do when called with real credentials
Connect it under the guard. Startup only; authenticated tool behavior not tested. The code names no credential variable; the guard pins the network to what the honeypot saw and logs every call.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; startup only; authenticated tool behavior not tested) on 2026-11-14 and scored it 82/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 20 s · 2 scenarios · 0 deviationsStatic findings
npx pg-lock-xray prisma/migrationsFix: Pin versions and sources; vendor anything fetched at install time.npx -y jsr publish --allow-dirtyFix: Pin versions and sources; vendor anything fetched at install time.npx pg-lock-xray --fix ./migration.sql --allow-writeFix: Pin versions and sources; vendor anything fetched at install time.expect(() => resolveContainedSqlPath("/etc/passwd", root)).toThrow(/Absolute/i);Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."/etc/passwd"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.npm install -g npm@latestFix: Pin the exact version (`[email protected]`, `==1.2.3`) so every install gets the bytes that were reviewed.return Ok(vec![analyze_sql_text(&input.sql, &input.source)]);Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.npx pg-lock-xray --mcpFix: Pin versions and sources; vendor anything fetched at install time.npx pg-lock-xray --fix ./drizzle/0001.sql --dry-runFix: Pin versions and sources; vendor anything fetched at install time.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.