@livx.cc/agentx@0.99.102
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 runtime credential flow can send a saved service token to an unrestricted configured endpoint, so a warning is warranted. The inspected source does not establish an unconsented default transfer to an unrelated recipient or another block-level attack.
Decision evidence
public snapshot- On macOS, the CLI can read a saved Para vault token; BODIFY_API_KEY can also supply the credential.
- The Bodify lookup accepts BODIFY_URL as its destination and sends the credential as a bearer token without validating the recipient.
- The CLI calls this lookup during startup, so the transfer occurs when a credential is available.
- The flagged agent locations describe project instructions, agent definitions, and repository worktree paths; they do not establish a separate agent control-surface attack.
- The manifest has a prepare Git-hooks command and a prepublish build command, with no preinstall, install, or postinstall hook.
- The default destination is the Bodify service, and the lookup retrieves configured application environment values.
- The credential transfer depends on a saved or environment-provided token and a CLI startup.
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.102.
See all versions of @livx.cc/agentx for other recorded verdicts.
- Review the evidence and your use of @livx.cc/agentx@0.99.102 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.