registry / @proagentstore/cli / 0.4.181
@proagentstore/cli@0.4.181
CLI for creating, publishing, and running ProAgentStore agents
AI Security Review
scanned 10d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the flagged process, shell, and network operations are tied to the CLI's runner and update functions. The inspected source does not establish unconsented data transfer or other concrete attack behavior.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The package runs when a user invokes its CLI; update checks run for the `up` command.
Impact
No concrete malicious impact was established.
Mechanism
The CLI manages its own cached releases and uses ProAgentStore service requests, MCP transports, and runner operations.
AI rationale
The manifest has no install lifecycle hook, and the flagged process, shell, and network operations are tied to the CLI's runner and update functions. The inspected source does not establish unconsented data transfer or other concrete attack behavior.
Decision evidence
public snapshotAI called this Clean at 93.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json exposes a CLI entrypoint and lists build, development, type-check, and packaging scripts; it has no install lifecycle hook.
- The updater installs another release of this same CLI into a payload directory, and the launcher selects a cached or bundled payload at runtime.
- Update status is sent through the package's configured ProAgentStore API path; update-log text is masked before it is included.
- The inspected process, terminal, filesystem, site-builder, and runner code is connected to CLI runner functions rather than an unrelated package-install action.
- The inspected dependency snapshots contain MCP client/server transports and Playwright browser APIs used by the runner.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShellWebSocket
HighEntropyStrings
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.181.
See all versions of @proagentstore/cli for other recorded verdicts.
- Review the evidence and your use of @proagentstore/cli@0.4.181 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.