@agentvault/openai-bridge@0.1.3
AgentVault OpenAI Codex bridge for encrypted owner messages and rooms
AI Security Review
scanned 15d ago · by lpm-firewall-aiThe inspected source shows a prepublish build hook, a CLI that discards captured child output, and an optional API key sent to the AgentVault API. These facts do not support the scanner’s exfiltration claims, so the package is clean.
Decision evidence
public snapshot- package.json points to the bundled CLI and declares only a prepublish build hook; it has no install lifecycle hook.
- The bundled bridge sends an optional AgentVault API key to its AgentVault capability endpoint, and validates the configured API URL as HTTPS.
- The CLI’s child-process wrapper discards captured output and kills processes that exceed its byte limit; this does not establish command-output exfiltration.
- The declared ws dependency exposes standard Node and browser entrypoints; its inspected runtime excerpt sets a WebSocket protocol header.
- No inspected source supports the scanner’s claim that command output is sent to an external endpoint or that an OpenAI credential is redirected to an unofficial gateway.
Source & flagged code
9 flaggedSource executes local commands and sends command output to an external endpoint.
dist/index.jsView on unpkg · L102411A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
dist/index.jsView on unpkg · L102411Findings
Affected versions and remediation
This report applies to @agentvault/openai-bridge@0.1.3.
See all versions of @agentvault/openai-bridge for other recorded verdicts.
- Review the evidence and your use of @agentvault/openai-bridge@0.1.3 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.