registry / @proagentstore/cli / 0.4.202
@proagentstore/cli@0.4.202
CLI for creating, publishing, and running ProAgentStore agents
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe package has no install lifecycle hook, and the flagged credential flows are provider model-list requests to the corresponding providers. Runner access and service installation are tied to explicit CLI use, with no evidence of unrelated data exfiltration or automatic persistence.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
User runs a CLI command; model-list lookups occur only when requested, and service setup requires the install-service option.
Impact
No unrelated credential collection, command-output exfiltration, or unrequested persistence was identified.
Mechanism
The CLI sends its ProAgentStore session to the ProAgentStore API and may use a provider key for a model-list request to that key’s own provider. Coding inspection uses bounded, validated repository reads and Git commands.
AI rationale
The package has no install lifecycle hook, and the flagged credential flows are provider model-list requests to the corresponding providers. Runner access and service installation are tied to explicit CLI use, with no evidence of unrelated data exfiltration or automatic persistence.
Evidence
~/.config/proagentstore/session.json
Network endpoints4
api.proagentstore.onlineapi.anthropic.comapi.openai.comgenerativelanguage.googleapis.com
Decision evidence
public snapshotAI called this Clean at 97.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package exposes a CLI entry point and has no install, preinstall, or postinstall lifecycle script.
- Provider API keys are used for model-list requests only when a relevant provider and key are present; the endpoints are the matching providers’ own APIs.
- Coding inspection is described as read-only, confined to the session work directory, and uses validated paths and fixed Git arguments.
- The runner contacts ProAgentStore’s API with the user’s ProAgentStore session token when the user runs `pags up`.
- Service installation is an explicit `pags up --install-service` option.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShellWebSocket
HighEntropyStringsUrlStrings
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/coding/inspect.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.202.
See all versions of @proagentstore/cli for other recorded verdicts.
- Review the evidence and your use of @proagentstore/cli@0.4.202 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.