@jait/gateway@0.1.857
⚠ Under reviewJait AI gateway — local-first AI coding agent with terminal, filesystem, and browser control
AI Security Review
scanned 14d ago · by lpm-firewall-aiInspected sources show an npm postinstall runtime installer, ordinary API client behavior, and session-scoped pi MCP setup, without confirming an attack. Required clean coverage cannot be completed within the citation limit, and a required binary file cannot provide a source citation, so the unresolved package-wide review requires manual review.
Decision evidence
public snapshot- The manifest has a postinstall hook that runs a local runtime installer.
- The web search tool reads configured API keys and an optional OpenAI base URL, then sends the key to that endpoint; the inspected code does not establish a malicious recipient or intent.
- Pi MCP configuration is written per session, and the ACP provider invokes provisioning when starting pi-based sessions.
- Required source coverage remains unresolved: the clean decision requires more citations than the schema allows, and one required path is binary.
- The inspected pi integration writes session-scoped configuration rather than changing global or project agent configuration.
Source & flagged code
27 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgPackage source references child process execution.
web-dist/assets/index-DdHs7TlK.jsView on unpkg · L141Findings
Affected versions and remediation
This report applies to @jait/gateway@0.1.857.
See all versions of @jait/gateway for other recorded verdicts.
- Review the evidence and your use of @jait/gateway@0.1.857 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.