registry / @proagentstore/cli / 0.4.121
@proagentstore/cli@0.4.121
CLI for creating, publishing, and running ProAgentStore agents
AI Security Review
scanned 18d ago · by lpm-firewall-aiInspected source supports normal CLI, authentication, updater, and runner behavior, with no install hook or concrete attack path found. The scanner’s execution and network indicators are insufficient to establish malicious behavior.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The CLI or runner is invoked for its ordinary commands; the update lookup occurs in the explicit update flow.
Impact
No attack impact was established from the inspected source.
Mechanism
The CLI authenticates to the ProAgentStore API, manages local runner processes, and performs repository checks. No inspected code showed a hidden credential recipient or unconsented installation action.
AI rationale
Inspected source supports normal CLI, authentication, updater, and runner behavior, with no install hook or concrete attack path found. The scanner’s execution and network indicators are insufficient to establish malicious behavior.
Evidence
package.jsondist/bootstrap.jsdist/index.jsdist/chunk-NNA7VZ6W.jsdist/browser-runner/local-artifact/runtime.jsdist/browser-runner/coding/repo.js
Network endpoints1
api.proagentstore.online
Decision evidence
public snapshotAI called this Clean at 89.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json defines a CLI entrypoint and has no install lifecycle hook.
- Saved sessions are used for authentication to the ProAgentStore API.
- The local artifact runtime reads selected source files as part of a run and records file metadata.
- The repository probe runs a bounded Git status query to report whether a work directory is a checkout.
Evidence against
- The scanner flags process execution, environment access, and network use, but inspected examples show runner and repository functions plus authentication to the configured ProAgentStore API.
- The updater’s registry lookup is part of the explicit CLI update flow; no concrete hidden transfer or destructive attack was established.
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 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/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.121.
See all versions of @proagentstore/cli for other recorded verdicts.
- Review the evidence and your use of @proagentstore/cli@0.4.121 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.