@livx.cc/agentx@0.99.42
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 2mo ago · by lpm-firewall-aiThe source implements a user-invoked AI-agent CLI with powerful but package-aligned capabilities. Its configured Bodify credential request is conditional and not persisted as a provider redirect, while no install-time execution or concrete exfiltration chain was found.
Decision evidence
public snapshot- The CLI can send an explicitly configured BODIFY_API_KEY to bodify.bod.ee to retrieve an app environment.
- The shell tool can launch commands, although its default child environment removes common secret variables.
- The manifest has no preinstall, install, or postinstall hook; prepare only sets a local Git hook path.
- The CLI runs only behind an import.meta.main guard.
- The Bodify request requires both BODIFY_API_KEY and BODIFY_APP_ID and does not persist a gateway redirect.
- No self-dependency, opaque payload loading, automatic credential harvesting, or unconsented AI-agent control-surface mutation was found.
Source & flagged code
7 flagged · loading sourcePackage source references a known benign dynamic code generation pattern.
dist/index.jsView on unpkg · L5355Manifest-reachable source sends a prompted API credential to a fixed unofficial gateway and persists the redirection.
dist/cli.jsView on unpkgFindings
Affected versions and remediation
This report applies to @livx.cc/agentx@0.99.42.
See all versions of @livx.cc/agentx for other recorded verdicts.
- Review the evidence and your use of @livx.cc/agentx@0.99.42 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.