registry / @proagentstore/cli / 0.4.137
@proagentstore/cli@0.4.137
CLI for creating, publishing, and running ProAgentStore agents
AI Security Review
scanned 18d ago · by lpm-firewall-aiThe scanner's execution and network signals map to user-invoked CLI updates and the package's authenticated runner features. The manifest has no install hook, and source inspection found no concrete attack behavior.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The user runs a CLI command such as `up`, starts a runner, or initiates a supported runner task.
Impact
No unrelated credential transfer, unconsented install-time mutation, or other concrete attack behavior was established.
Mechanism
The CLI updates its own package on `up`, validates login sessions with the PAGS API, and routes Website Builder calls through a run-specific broker. Repository operations use supplied settings and guard against cloning into non-empty user folders.
AI rationale
The scanner's execution and network signals map to user-invoked CLI updates and the package's authenticated runner features. The manifest has no install hook, and source inspection found no concrete attack behavior.
Network endpoints1
api.proagentstore.online
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest points the CLI to its bootstrap and lists only build, development, and type-check scripts; it declares no install lifecycle hook.
- The bootstrap checks for a newer release only when the user runs the `up` command, and its update path installs this package.
- The login flow sends the received session token to the package's configured PAGS API for validation and saves it locally.
- Website Builder tasks use a broker URL tied to the run and send requests with that run's broker token; the runner launches the local author for that task type.
- Coding sessions use the supplied repository settings, and repository setup refuses to clone into a non-empty user folder.
- The coding runtime advertises its session and inspection capabilities to PAGS.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShellWebSocket
Source & flagged code
7 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/index.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = @proagentstore/cli@0.4.50
matchedIdentity = npm:QHByb2FnZW50c3RvcmUvY2xp:0.4.50
similarity = 0.423
summary = stored previous version shares package body but lacks this dangerous source file
Critical
Previous Version Dangerous Delta
This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/index.jsView on unpkg1364if (restarter === "command") {
L1365: deps.spawn(process.env[RESTART_COMMAND_ENV], { shell: true, detached: true, stdio: "ignore", env: process.env }).unref();
L1366: deps.exit(0);
Findings
1 Critical5 High3 Medium4 Low
CriticalPrevious Version Dangerous Deltadist/index.js
HighChild Processdist/browser-runner/site-builder/runtime.js
HighShelldist/index.js
HighSame File Env Network Executiondist/index.js
HighCommand Output Exfiltrationdist/index.js
HighSemantic Analysis Limiteddist/browser-runner/coding/repo.js#virtual:normalized:round1
MediumDynamic Requiredist/browser-runner/coding/runtime.js
MediumNetwork
MediumEnvironment Vars
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @proagentstore/cli@0.4.137.
See all versions of @proagentstore/cli for other recorded verdicts.
- Review the evidence and your use of @proagentstore/cli@0.4.137 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.