registry / @proagentstore/cli / 0.4.206
@proagentstore/cli@0.4.206
CLI for creating, publishing, and running ProAgentStore agents
AI Security Review
scanned 22h ago · by lpm-firewall-aiThe inspected source ties local process execution to an explicit tailoring feature and routes model-list API keys to their corresponding providers. The scanner's exfiltration and persistence leads were not substantiated by the reviewed excerpts.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
The CLI's documented commands and local runner features.
Impact
No malicious impact was established from the reviewed excerpts.
Mechanism
Inspected process execution supports local agent tasks; provider keys are used for requests to their own provider.
AI rationale
The inspected source ties local process execution to an explicit tailoring feature and routes model-list API keys to their corresponding providers. The scanner's exfiltration and persistence leads were not substantiated by the reviewed excerpts.
Decision evidence
public snapshotAI called this Clean at 82.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package is a CLI for creating, publishing, and running ProAgentStore agents, with `pags` as its command entry point.
- The added local artifact runtime describes drafting from one approved job lead and the owner's source files, using a signed-in local CLI.
- The model-list handler uses a provider key only for a request to that provider's own model-list endpoint.
- The API-key path in the local artifact runtime stops the run when a provider API key would reach the CLI.
Evidence against
- The scanner flags command output exfiltration and persistence, but the inspected excerpts did not establish either behavior.
- The package can spawn local commands for its tailoring feature, so command execution is present but has a stated local purpose.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShellWebSocket
Source & flagged code
10 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
2 Critical5 High5 Medium5 Low
CriticalCommand Output Exfiltrationdist/index.js
CriticalPrevious Version Dangerous Deltadist/browser-runner/local-artifact/runtime.js
HighChild Processdist/browser-runner/site-builder/runtime.js
HighShelldist/browser-runner/coding/windows-runner-live.js
HighSame File Env Network Executiondist/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 Persistencedist/index.js
Affected versions and remediation
This report applies to @proagentstore/cli@0.4.206.
See all versions of @proagentstore/cli for other recorded verdicts.
- Review the evidence and your use of @proagentstore/cli@0.4.206 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.