registry / @proagentstore/cli / 0.4.129
@proagentstore/cli@0.4.129
CLI for creating, publishing, and running ProAgentStore agents
AI Security Review
scanned 18d ago · by lpm-firewall-aiThe inspected source supports ordinary CLI, runner, and preflight behavior. Scanner signals for shell execution, child processes, environment access, and network use are accounted for by configured runner restart, fixed local probes, and API requests; no concrete attack was established.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Running the CLI; runner restart behavior activates during configured restart or update flows.
Impact
No confirmed malicious effect was established from the inspected source.
Mechanism
The preflight performs local probes, the repository check runs fixed git arguments, and the background runner builds its restart command from the CLI executable and runner arguments.
AI rationale
The inspected source supports ordinary CLI, runner, and preflight behavior. Scanner signals for shell execution, child processes, environment access, and network use are accounted for by configured runner restart, fixed local probes, and API requests; no concrete attack was established.
Decision evidence
public snapshotAI called this Clean at 88.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json points the CLI to dist/bootstrap.js and its payload to dist/index.js; its listed scripts are build, dev, and typecheck.
- The native preflight uses bounded execFile probes for local machine and device state.
- The shell restart path runs a configured restart command; background startup constructs that command from the CLI executable and runner arguments.
- The repository check invokes git with fixed arguments and the selected working directory.
- API and relay requests use the ProAgentStore API default and the package’s session token.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShellWebSocket
HighEntropyStringsUrlStrings
Source & flagged code
7 flaggeddist/browser-runner/native/preflight.jsView file
17*/
L18: import { execFile } from "node:child_process";
L19: import { arch as osArch, platform as osPlatform } from "node:os";
High
Child Process
Package source references child process execution.
dist/browser-runner/native/preflight.jsView on unpkg · L17dist/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 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/native/preflight.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.129.
See all versions of @proagentstore/cli for other recorded verdicts.
- Review the evidence and your use of @proagentstore/cli@0.4.129 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.