@livx.cc/agentx@0.99.112
Edge-native AI agent runtime — drives a virtual filesystem via any LLM (ai.libx.js). Same bytes run in node, browser, or edge.
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe flagged CLI credential flow uses a Para vault token to retrieve Bodify app environment values, with a Bodify-specific endpoint and app selection. The inspected agent, shell, and MCP code does not establish an attack surface.
Decision evidence
public snapshot- package.json points to the CLI and runtime entrypoints; its prepare script configures the package repository's Git hooks, and prepublishOnly builds the package.
- The CLI reads a Para vault token from macOS Keychain or accepts BODIFY_API_KEY, then uses it to fetch the selected Bodify app's environment from the configured Bodify endpoint.
- CLI startup calls the Bodify environment loader before assembling provider keys; the retrieved values are added to the process environment.
- The flagged CLI location handles Git worktree paths; the declarations expose agent definitions, and the runtime reads instruction files from the current working directory.
- The shell tool runs the command supplied to it and is documented as bound to a caller-provided working directory.
- The MCP client connects its transport and sends the standard initialization request.
Source & flagged code
12 flagged · loading sourcePackage source references child process execution.
dist/tools.shell.jsView on unpkg · L891Findings
Affected versions and remediation
This report applies to @livx.cc/agentx@0.99.112.
See all versions of @livx.cc/agentx for other recorded verdicts.
- Review the evidence and your use of @livx.cc/agentx@0.99.112 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.