@agentvault/openai-bridge@0.1.7
AgentVault OpenAI Codex bridge for encrypted owner messages and rooms
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe inspected source supports ordinary bridge behavior: explicit local login, constrained Codex execution, and replies delivered through AgentVault. The scanner's command-output finding is not supported by this path, which disables shell access and sends the model reply to the addressed conversation.
Decision evidence
public snapshot- The package manifest lists a prepublish-only build hook and the ws runtime dependency.
- The CLI uses the AgentVault API origin and requires HTTPS; Codex login is a separate interactive command.
- Codex runs with a dedicated home directory and a read-only workspace.
- A turn handles an owner message or addressed room message, disables filesystem, shell, web, and integration tools, then delivers the reply through the bridge.
- The ws dependency exposes its normal Node and browser entrypoints, has no install lifecycle hook, and the flagged operation sets a WebSocket protocol header.
Source & flagged code
9 flaggedSource executes local commands and sends command output to an external endpoint.
dist/index.jsView on unpkg · L103286A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
dist/index.jsView on unpkg · L103286Findings
Affected versions and remediation
This report applies to @agentvault/openai-bridge@0.1.7.
See all versions of @agentvault/openai-bridge for other recorded verdicts.
- Review the evidence and your use of @agentvault/openai-bridge@0.1.7 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.