registry / @proagentstore/cli / 0.4.135
@proagentstore/cli@0.4.135
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 flagged runtime behavior is consistent with user-invoked CLI and runner functions. Scanner signals such as shell execution and networking did not establish a concrete attack surface.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A user runs the CLI or starts a runner task that invokes the relevant feature.
Impact
No unauthorized credential transfer, persistence, destructive action, or unrelated control-surface mutation was established.
Mechanism
The CLI checks or installs releases through its update flow; runner tools use a validated broker route, and repository operations invoke Git for the requested clone.
AI rationale
The manifest has no install lifecycle hook, and inspected flagged runtime behavior is consistent with user-invoked CLI and runner functions. Scanner signals such as shell execution and networking did not establish a concrete attack surface.
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 entry point and lists only build, dev, and typecheck scripts; it has no install lifecycle hook.
- The bootstrap selects the bundled or cached CLI payload, and update behavior is gated by the user’s `up` argument.
- The runner update code refuses unsafe restart conditions and installs a version only through its update flow.
- The site-builder validates a run-scoped broker URL and sends tool requests to that broker; deployment is separately presented for owner review.
- Repository cloning uses the supplied repository URL and disables interactive Git prompts.
Evidence against
- The package includes dynamic loading, network access, and child-process calls, but inspected contexts tie them to CLI updates, local runner tasks, or repository operations; no concrete attack behavior was established.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShellWebSocket
Source & flagged code
7 flaggeddist/browser-runner/site-builder/runtime.jsView file
32*/
L33: import { spawn as nodeSpawn } from "node:child_process";
L34: import { randomBytes } from "node:crypto";
High
Child Process
Package source references child process execution.
dist/browser-runner/site-builder/runtime.jsView on unpkg · L32dist/index.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = @proagentstore/cli@0.4.50
matchedIdentity = npm:QHByb2FnZW50c3RvcmUvY2xp:0.4.50
similarity = 0.423
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/site-builder/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.135.
See all versions of @proagentstore/cli for other recorded verdicts.
- Review the evidence and your use of @proagentstore/cli@0.4.135 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.