@livx.cc/agentx@0.99.48
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 14d ago · by lpm-firewall-aiThe credential is sent only when the user has configured Bodify credentials, but BODIFY_URL can redirect it to an unrestricted destination. This is a concrete conditional credential-forwarding risk, not evidence of default credential theft or an install-time attack.
Decision evidence
public snapshot- The CLI reads BODIFY_API_KEY and BODIFY_APP_ID, then allows BODIFY_URL to replace the default gateway without restricting its destination.
- CLI startup calls the secret-fetch routine before continuing, so the configured key is sent automatically when both variables are set.
- The Bodify secret-fetch feature is inactive unless both BODIFY_API_KEY and BODIFY_APP_ID are present.
- The default recipient is the package’s Bodify gateway; no npm install hook performs this request.
- The inspected agent-related locations describe project worktrees, typed subagents, and reading project instruction files; they do not show install-time agent configuration mutation.
Source & flagged code
7 flagged · loading sourcePackage source references a known benign dynamic code generation pattern.
dist/index.jsView on unpkg · L5791Manifest-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.48.
See all versions of @livx.cc/agentx for other recorded verdicts.
- Review the evidence and your use of @livx.cc/agentx@0.99.48 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.