@livx.cc/agentx@0.99.116
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-aiSource inspection found no malicious behavior. The scanner signals resolve to ordinary package setup and user-invoked runtime capabilities, while the CLI's conditional vault request targets Bodify.
Decision evidence
public snapshot- package.json defines prepare as local Git-hook configuration and prepublishOnly as a build; neither is an npm install hook.
- The CLI reads a Bodify vault token from the configured environment or Para keychain, then uses it for the Bodify secrets endpoint only when a token exists.
- The Bodify lookup runs during CLI startup, where its returned values supply environment settings for the agent.
- The reviewed agent integrations read project instructions and load subagent definitions only when subagents and an agents directory are configured.
- Shell execution is exposed as an invoked tool, and MCP child processes use commands from their configured server specifications.
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.116.
See all versions of @livx.cc/agentx for other recorded verdicts.
- Review the evidence and your use of @livx.cc/agentx@0.99.116 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.