postgres-pro

Fail

Audited by Runlayer on Mar 7, 2026

Risk Level: HIGH
Scan Summary
Max Score
91%
Files
6
Flagged
5
Chunks
10
Flagged Files (5)
postgres-pro/references/jsonb.mdHIGH
90.6%

Tool passed security scan

Malicious tool definition detected

postgres-pro/references/replication.mdMEDIUM
89.1%

Malicious tool definition detected

postgres-pro/references/extensions.mdMEDIUM
78.5%

Tool passed security scan

Malicious tool definition detected

postgres-pro/references/maintenance.mdLOW
70.2%

Tool passed security scan

Malicious tool definition detected

Description: blocked_locks.pid JOIN pg_catalog.pg_locks blocking_locks ON blocking_locks.locktype = blocked_locks.locktype AND blocking_locks.database IS NOT DISTINCT FROM blocked_locks.database AND blocking_locks.relation IS NOT DISTINCT FROM blocked_locks.relation AND blocking_locks.page IS NOT DISTINCT FROM blocked_locks.page AND blocking_locks.tuple IS NOT DISTINCT FROM blocked_locks.tuple AND blocking_locks.virtualxid IS NOT DISTINCT FROM blocked_locks.virtualxid AND blocking_locks.transact

postgres-pro/SKILL.mdLOW
50.7%

Tool passed security scan

Passed Files (1)Click to expand
postgres-pro/references/performance.mdOK
48.3%

Tool passed security scan

Audit Metadata
Max File Score
91%
Classification
KNOWN_SERVER_KNOWN_TOOL_LIST
Files Scanned
6
Files Flagged
5
Chunks Analyzed
10
Analyzed
Mar 7, 2026, 11:42 AM
Security Audit — runlayer — postgres-pro