registry / @proagentstore/cli / 0.4.178
@proagentstore/cli@0.4.178
⚠ Under reviewCLI for creating, publishing, and running ProAgentStore agents
AI Security Review
scanned 13d ago · by lpm-firewall-aiThe inspected manifest and CLI source do not establish malicious behavior. The selected Commander dependency could not be verified, so the result is manual review rather than a clean verdict.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The CLI loads and uses its declared Commander dependency when its entrypoint runs.
Impact
The available source does not establish an attack, but the unresolved dependency prevents a clean determination.
Mechanism
The package delegates command parsing to Commander, whose selected registry source was not present for inspection.
AI rationale
The inspected manifest and CLI source do not establish malicious behavior. The selected Commander dependency could not be verified, so the result is manual review rather than a clean verdict.
Evidence
package.jsondist/index.js
Decision evidence
public snapshotAI called this Manual Review at 76.0% confidence as Unknown with medium false-positive risk.
AI review observations
- The manifest lists Commander as a runtime dependency, and the CLI imports it and invokes its argument parser.
- The source for this selected dependency was unavailable in the inspected package snapshot, so its behavior could not be verified.
Evidence against
- The manifest’s scripts list contains no preinstall, install, or postinstall hook.
- No concrete attack was established in the inspected CLI parser path.
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/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.178.
See all versions of @proagentstore/cli for other recorded verdicts.
- Review the evidence and your use of @proagentstore/cli@0.4.178 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.