@livx.cc/agentx@0.99.36
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-aiSource inspection found no registry-install lifecycle hook or covert payload. Network, credential, shell, and file operations are reachable through explicit CLI and agent actions consistent with the package's coding-agent function.
Decision evidence
public snapshot- The user-run CLI can send a configured Bodify API key to the configured Bodify service.
- The explicit update option queries npm and can launch Bun to update this package.
- The manifest has no preinstall, install, or postinstall hook.
- The CLI entry point runs only when invoked directly.
- Bodify retrieval requires both BODIFY_API_KEY and BODIFY_APP_ID; no source shows unrelated credential collection or exfiltration.
- Project writes are normal agent session, settings, permission, and instruction files after user CLI use.
Source & flagged code
8 flagged · loading sourcePackage source references a known benign dynamic code generation pattern.
dist/index.jsView on unpkg · L5035Manifest-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.36.
See all versions of @livx.cc/agentx for other recorded verdicts.
- Review the evidence and your use of @livx.cc/agentx@0.99.36 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.