@livx.cc/agentx@0.99.100
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 CLI forwards a Bodify credential to the configured BODIFY_URL without checking that the destination is the intended Bodify service, so conditional credential exposure remains. The separate agent-integration hints resolve to ordinary local runtime behavior and do not establish agent configuration hijacking.
Decision evidence
public snapshot- The CLI can obtain a token from the Para Settings keychain and uses it for Bodify secrets when no BODIFY_API_KEY is set.
- At CLI startup, the package loads its environment and calls the Bodify secrets function.
- That function defaults to Bodify but accepts BODIFY_URL as the request destination and sends the token as a bearer credential without a destination allowlist in the inspected code.
- The flagged CLI agent-configuration location builds a local .claude/worktrees path for an explicitly requested worktree; the other inspected locations describe agent definitions and project-instruction loading.
- The package exposes the CLI as a user-run binary, while its prepare script configures Git hooks.
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.100.
See all versions of @livx.cc/agentx for other recorded verdicts.
- Review the evidence and your use of @livx.cc/agentx@0.99.100 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.