registry / @proagentstore/cli / 0.4.101
@proagentstore/cli@0.4.101
CLI for creating, publishing, and running ProAgentStore agents
AI Security Review
scanned 18d ago · by lpm-firewall-aiThe manifest has no install hook, and inspected runtime behavior aligns with the CLI’s stated functions. Scanner flags for shell, network, and process use did not establish concrete attack behavior.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
No attack trigger was identified; updates require the `up` command, and local artifact generation is task-driven.
Impact
No confirmed unauthorized credential transfer, destructive behavior, or hidden execution was established.
Mechanism
Inspected process calls perform package update or local CLI and Git operations; login sends its session to the package’s fixed service endpoint.
AI rationale
The manifest has no install hook, and inspected runtime behavior aligns with the CLI’s stated functions. Scanner flags for shell, network, and process use did not establish concrete attack behavior.
Decision evidence
public snapshotAI called this Clean at 97.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest lists build, development, and typecheck scripts, with no install lifecycle hook.
- The bootstrap checks for and installs an update only for the explicit `up` command.
- Login validates the session against the package’s fixed ProAgentStore API endpoint.
- The local artifact runtime bounds source inputs and creates a fresh output folder within the workspace.
- Repository inspection runs a fixed Git query against the selected work directory.
Evidence against
- The flagged process execution supports local CLI and repository operations; inspected source did not establish hidden command execution or unrelated data transfer.
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.101.
See all versions of @proagentstore/cli for other recorded verdicts.
- Review the evidence and your use of @proagentstore/cli@0.4.101 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.