registry / @proagentstore/cli / 0.4.180
@proagentstore/cli@0.4.180
CLI for creating, publishing, and running ProAgentStore agents
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe scanner flags map to intended CLI and agent-runner behavior, with update checks triggered by `up` and runner requests protected by local authentication and input validation. Source inspection found no concrete malicious behavior or unconsented install-time action.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Updates are checked when the `up` command is invoked; runner operations are reached through the local runtime.
Impact
No unsolicited credential disclosure, install-time mutation, or concealed persistence was established.
Mechanism
The launcher installs a newer release into its payload directory. Runner operations validate their scope and token, and the local server requires authentication and rejects browser-origin requests.
AI rationale
The scanner flags map to intended CLI and agent-runner behavior, with update checks triggered by `up` and runner requests protected by local authentication and input validation. Source inspection found no concrete malicious behavior or unconsented install-time action.
Decision evidence
public snapshotAI called this Clean at 90.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest defines no npm install lifecycle hook; its listed scripts are for building, development, type checking, and package testing.
- The launcher checks for updates only when `up` is invoked and installs the package into its payload directory.
- The runner validates the GitHub scope and runner token. Its local server rejects browser-origin requests and requires a bearer token.
- The reviewed runtime and dependency paths correspond to the package’s CLI, agent, MCP, and browser-runner functions; no concrete attack behavior was identified.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShellWebSocket
HighEntropyStringsUrlStrings
Source & flagged code
9 flaggeddist/browser-runner/site-builder/runtime.jsView file
32*/
L33: import { spawn as nodeSpawn } from "node:child_process";
L34: import { randomBytes } from "node:crypto";
High
Child Process
Package source references child process execution.
dist/browser-runner/site-builder/runtime.jsView on unpkg · L32dist/browser-runner/coding/windows-runner-live.jsView file
59busy: async (dir) => {
L60: const ps = spawnSync("powershell", ["-NoProfile", "-Command", `(Get-CimInstance Win32_Process -Filter "Name='Runner.Worker.exe'" | Where-Object { $_.ExecutablePath -like '${dir.rep...
L61: return ps.status === 0 && Number.parseInt(String(ps.stdout).trim(), 10) > 0;
High
Shell
Package source references shell execution.
dist/browser-runner/coding/windows-runner-live.jsView on unpkg · L59Findings
1 Critical6 High5 Medium4 Low
CriticalPrevious Version Dangerous Deltadist/browser-runner/coding/headless.js
HighChild Processdist/browser-runner/site-builder/runtime.js
HighShelldist/browser-runner/coding/windows-runner-live.js
HighSame File Env Network Executiondist/browser-runner/coding/actions-runner.js#virtual:normalized:round1
HighCommand Output Exfiltrationdist/index.js
HighSandbox Evasion Gated Capabilitydist/browser-runner/coding/actions-runner.js
HighSemantic Analysis Limiteddist/browser-runner/coding/actions-runner.js#virtual:normalized:round1
MediumDynamic Requiredist/browser-runner/coding/runtime.js
MediumNetwork
MediumEnvironment Vars
Medium
Affected versions and remediation
This report applies to @proagentstore/cli@0.4.180.
See all versions of @proagentstore/cli for other recorded verdicts.
- Review the evidence and your use of @proagentstore/cli@0.4.180 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.