registry / @proagentstore/cli / 0.4.186
@proagentstore/cli@0.4.186
CLI for creating, publishing, and running ProAgentStore agents
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe flagged network and command capabilities are consistent with an agent platform CLI and its runner operations. PAGS credentials go to the PAGS API, provider keys are used for their own provider's model endpoint, and runner setup is action-driven; the package declares no install lifecycle hook.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
CLI commands and runner operations initiated by the user; provider model lookup when requested.
Impact
No unauthorized credential transfer or unrelated automatic action was identified.
Mechanism
Sends PAGS credentials to the PAGS API and uses provider API keys for that provider's model-list endpoint. Runner setup uses the requested GitHub scope and registration token.
AI rationale
The flagged network and command capabilities are consistent with an agent platform CLI and its runner operations. PAGS credentials go to the PAGS API, provider keys are used for their own provider's model endpoint, and runner setup is action-driven; the package declares no install lifecycle hook.
Network endpoints5
api.proagentstore.onlineapi.anthropic.comapi.openai.comgenerativelanguage.googleapis.comgithub.com
Decision evidence
public snapshotAI called this Clean at 92.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package describes itself as a CLI for creating, publishing, and running ProAgentStore agents.
- The package has no install, preinstall, or postinstall lifecycle script.
- Authenticated PAGS requests require a PAGS token and send it to the configured PAGS API base.
- The model-list check uses an available provider key for one request to that provider and does not return the key.
- The Actions runner setup is started through an explicit runner-job action.
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
2 Critical5 High5 Medium4 Low
CriticalCommand Output Exfiltrationdist/index.js
CriticalPrevious Version Dangerous Deltadist/browser-runner/coding/actions-runner.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.186.
See all versions of @proagentstore/cli for other recorded verdicts.
- Review the evidence and your use of @proagentstore/cli@0.4.186 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.