registry / aclade-agent / 1.2.2
aclade-agent@1.2.2
Aclade Local AI Agent Connector
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe execution, networking, daemon gate, and runtime installation findings are consistent with the connector's active code structure and token-configured operation. Static inspection found no concrete malicious behavior or install-time attack chain.
Static reason
One or more suspicious static signals were detected.
Trigger
Running the entrypoint with a supplied or previously configured connection token activates the connector.
Impact
Requested tasks can access files and execute commands with the running user's permissions; inspected source shows no separate covert attack.
Mechanism
The connector polls its configured host, executes received tasks, returns results, and checks npm for updates to itself.
AI rationale
The execution, networking, daemon gate, and runtime installation findings are consistent with the connector's active code structure and token-configured operation. Static inspection found no concrete malicious behavior or install-time attack chain.
Evidence
.aclade-agent.json.aclade-agent.pid.aclade-agent.log
Network endpoints2
aclade.comregistry.npmjs.org/aclade-agent/latest
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json has no install lifecycle hooks or runtime self-dependency.
- dist/index.js exits before polling when no connection token is configured.
- src/index.ts accepts caller-supplied connection tokens, hosts, and workspace paths.
- Shell execution implements remotely requested connector tasks; results return to the configured connector host.
- Runtime package installation updates aclade-agent itself from npm, rather than installing an unrelated payload.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
4 flaggeddist/index.jsView file
38const https = __importStar(require("https"));
L39: const child_process = __importStar(require("child_process"));
L40: const fs = __importStar(require("fs"));
High
61* The agent already self-updates through npm, so telling a customer to run
L62: * `npx playwright install` by hand was busywork we could just do. playwright-core
L63: * ships the same installer the `playwright` package exposes, so we invoke it
...
L74: console.log("=> Preparing the browser (one-time download, ~50MB)…");
L75: const proc = child_process.spawn(process.execPath, [cli, "install", "chromium", "--only-shell", "--no-progress"], {
L76: stdio: ["ignore", "pipe", "pipe"],
High
Runtime Package Install
Package source invokes a package manager install command at runtime.
dist/index.jsView on unpkg · L61src/index.tsView file
383const proc = child_process.spawn(input.command, [], { // nosemgrep: javascript.lang.security.detect-child-process.detect-child-process
L384: shell: true,
L385: cwd: input.cwd ? resolvePath(input.cwd) : workspaceRoot,
Findings
4 High3 Medium5 Low
HighChild Processdist/index.js
HighShellsrc/index.ts
HighSandbox Evasion Gated Capabilitysrc/index.ts
HighRuntime Package Installdist/index.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to aclade-agent@1.2.2.
See all versions of aclade-agent for other recorded verdicts.
- Review the evidence and your use of aclade-agent@1.2.2 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.