registry / @proagentstore/cli / 0.4.113
@proagentstore/cli@0.4.113
CLI for creating, publishing, and running ProAgentStore agents
AI Security Review
scanned 18d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and inspected network and process behavior maps to explicit CLI functions and scoped runner tasks. The flagged primitives do not establish malicious behavior or an unresolved attack surface.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The user runs the CLI or starts a runner task; the bootstrap update check is limited to the update command.
Impact
No install-time mutation, credential export to an unrelated recipient, or other confirmed attack effect was established.
Mechanism
Login uses the fixed service API, while runner file access and repository operations have path and directory checks.
AI rationale
The manifest has no install lifecycle hook, and inspected network and process behavior maps to explicit CLI functions and scoped runner tasks. The flagged primitives do not establish malicious behavior or an unresolved attack surface.
Network endpoints2
api.proagentstore.onlinemcp.proagentstore.online
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json exposes a CLI binary; its scripts contain build, development, and typecheck commands, with no install lifecycle hook.
- The bootstrap checks for an update only when the user runs the update command.
- Login validates the session against the package's fixed ProAgentStore API endpoint.
- The local artifact runner restricts source paths and refuses provider API-key authentication before starting its local engine.
- The MCP proxy is an explicit CLI command that defaults to the ProAgentStore MCP endpoint.
- Repository setup reuses existing checkouts and refuses to clone into non-empty non-repository folders.
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 unpkg1292if (restarter === "command") {
L1293: deps.spawn(process.env[RESTART_COMMAND_ENV], { shell: true, detached: true, stdio: "ignore", env: process.env }).unref();
L1294: 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.113.
See all versions of @proagentstore/cli for other recorded verdicts.
- Review the evidence and your use of @proagentstore/cli@0.4.113 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.