@jait/gateway@0.1.941
Jait AI gateway — local-first AI coding agent with terminal, filesystem, and browser control
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe postinstall hook performs an automatic third-party runtime installation, leaving a concrete lifecycle supply-chain risk that warrants a warning. The inspected behavior does not show credential theft, account manipulation, or other malicious activity.
Decision evidence
public snapshot- The package postinstall calls a runtime provisioner automatically during installation.
- When the pinned Graphify runtime is absent, the provisioner creates a Python virtual environment and runs pip to install Graphify.
- The gateway also starts this optional runtime on normal startup, supporting a product feature rather than a hidden install-only action.
- The cited Git operations fetch or clone caller-selected repositories; they do not show automatic account changes.
- The pi integration writes session-scoped MCP configuration instead of changing global or project configuration.
- Browser search uses configured API keys for a validated provider endpoint; the inspected source does not show a transfer to an unrelated recipient.
- The postinstall hook installs executable third-party Python package code without a separate user prompt.
- The source pins the Graphify package version and places the managed runtime in Jait's state directory.
Source & flagged code
28 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgPackage source references child process execution.
bin/safe-update.mjsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @jait/gateway@0.1.941.
See all versions of @jait/gateway for other recorded verdicts.
- Review the evidence and your use of @jait/gateway@0.1.941 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.