registry / @proagentstore/cli / 0.4.105
@proagentstore/cli@0.4.105
CLI for creating, publishing, and running ProAgentStore agents
AI Security Review
scanned 18d ago · by lpm-firewall-aiSource inspection found no install lifecycle hook or concrete attack behavior. The flagged network and execution primitives are used by the package’s documented CLI and runner functions, with the reviewed credential request directed to its own API.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The CLI’s login, runner, repository, or `up` update flows are invoked.
Impact
No confirmed harmful effect was established.
Mechanism
These flows contact the package’s API or launch feature-specific subprocesses; the inspected excerpts show no unrelated credential recipient or install-time execution.
AI rationale
Source inspection found no install lifecycle hook or concrete attack behavior. The flagged network and execution primitives are used by the package’s documented CLI and runner functions, with the reviewed credential request directed to its own API.
Network endpoints1
api.proagentstore.online
Decision evidence
public snapshotAI called this Clean at 93.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json exposes a CLI and lists only build, development, and type-check scripts; it declares no install lifecycle hook.
- Login sends the received session token to the package’s fixed ProAgentStore API for validation.
- Local artifact tasks validate their type and workspace source paths before launching the selected engine in a run-specific scratch directory.
- Repository subprocesses perform Git inspection in the requested working directory; existing nonempty owner folders are left untouched.
- The bootstrap checks for updates when invoked with `up`; payload installation uses a separate prefix for the same package.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShellWebSocket
HighEntropyStringsUrlStrings
Source & flagged code
7 flaggeddist/browser-runner/local-artifact/runtime.jsView file
22*/
L23: import { spawn as nodeSpawn } from "node:child_process";
L24: import { createHash } from "node:crypto";
High
Child Process
Package source references child process execution.
dist/browser-runner/local-artifact/runtime.jsView on unpkg · L22dist/index.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = @proagentstore/cli@0.4.50
matchedIdentity = npm:QHByb2FnZW50c3RvcmUvY2xp:0.4.50
similarity = 0.462
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 unpkg1286if (restarter === "command") {
L1287: deps.spawn(process.env[RESTART_COMMAND_ENV], { shell: true, detached: true, stdio: "ignore", env: process.env }).unref();
L1288: deps.exit(0);
Findings
1 Critical5 High3 Medium4 Low
CriticalPrevious Version Dangerous Deltadist/index.js
HighChild Processdist/browser-runner/local-artifact/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.105.
See all versions of @proagentstore/cli for other recorded verdicts.
- Review the evidence and your use of @proagentstore/cli@0.4.105 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.