@solongate/proxy
AI tool security proxy: protect any AI tool server with customizable policies, path/command constraints, rate limiting, and audit logging. No code changes required.
This report shows the evidence for @solongate/proxy@0.90.65. 11 of 244 known versions are blocked or flagged. The newest version, 0.91.25, is flagged. See all versions.
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThis package has no npm lifecycle hook, but its explicit global setup persistently modifies broad AI-agent control surfaces, uploads conversation content, and remotely updates the executed hooks. These concrete capabilities exceed a normal local proxy and create a high-risk data-exfiltration and remote-code-update path.
Decision evidence
public snapshot- The global installer registers wildcard command hooks in Codex, including hooks that record prompts and replies.
- The conversation hook sends captured prompt or reply text to the configured SolonGate API.
- The installed guard downloads newer hook code and atomically replaces its own files.
- The installer targets multiple unrelated AI-client configuration directories and locks its protection files.
- package.json has no preinstall, install, or postinstall lifecycle hook.
- The hook installation path is invoked by package commands rather than npm installation.
Source & flagged code
20 flagged · loading sourcePackage source references child process execution.
dist/tui/index.jsView on unpkg · L143Findings
Affected versions and remediation
This report applies to @solongate/proxy@0.90.65.
The versions list below shows the verdict for each recorded version.
- Avoid installing @solongate/proxy@0.90.65. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.