0xray@4.1.2
Three-subsystem autonomous engine. The suit powers the agent you already run: memory, judgement, payments, and the wake.
AI Security Review
scanned 4d ago · by lpm-firewall-aiSource inspection did not establish malicious install-time behavior. The separate bridge setup capability can add package-provided MCP servers to an agent plugin, so retain a warning for the unresolved extension setup risk.
Decision evidence
public snapshot- The package has an npm postinstall hook, whose runner links vendored Repertoire and prints a separate wear command.
- A bridge setup helper can write an MCP configuration into an agent plugin directory; its activation through an npm install hook was not established.
- The CLI wear command delegates to a Cursor hook script.
- The postinstall runner does not call the bridge setup helper; the inspected runtime path only links the vendored package and prints the wear command.
Source & flagged code
25 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgPackage source references child process execution.
dist/security/security-scanner.jsView on unpkg · L6Findings
Affected versions and remediation
This report applies to 0xray@4.1.2.
See all versions of 0xray for other recorded verdicts.
- Review the evidence and your use of 0xray@4.1.2 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.