registry / @proagentstore/cli / 0.4.177
@proagentstore/cli@0.4.177
CLI for creating, publishing, and running ProAgentStore agents
AI Security Review
scanned 13d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the inspected high-risk calls support explicit CLI runner features. The scanner signals did not establish malicious behavior.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Users invoke CLI commands or request runner tasks.
Impact
No confirmed unauthorized changes, credential disclosure, or harmful execution was established.
Mechanism
Runner setup, terminal operations, and site-authoring launch are tied to those features; the inspected release lookup targets GitHub.
AI rationale
The manifest has no install lifecycle hook, and the inspected high-risk calls support explicit CLI runner features. The scanner signals did not establish malicious behavior.
Network endpoints2
api.proagentstore.onlineapi.github.com/repos/actions/runner/releases/latest
Decision evidence
public snapshotAI called this Clean at 95.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json maps the CLI to dist/bootstrap.js and lists build, development, typecheck, and package-test scripts, with no install lifecycle hook.
- The inspected runtime operation in dist/index.js is runner restart handling that exits when service mode applies.
- Inspected dependency manifests and entrypoints identify the MCP SDK, Playwright MCP, and Playwright; their inspected code provides MCP transports and browser automation.
- The flagged process and shell operations support explicit runner, repository, terminal, and site-authoring features.
- The Actions runner code fetches release information from GitHub and configures the runner using request-provided inputs.
Evidence against
- Static process, shell, environment, and network signals correspond to the package’s runner features; inspection did not establish an attack.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShell
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/index.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
MediumInstall Persistence
Affected versions and remediation
This report applies to @proagentstore/cli@0.4.177.
See all versions of @proagentstore/cli for other recorded verdicts.
- Review the evidence and your use of @proagentstore/cli@0.4.177 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.