registry / @proagentstore/cli / 0.4.100
@proagentstore/cli@0.4.100
CLI for creating, publishing, and running ProAgentStore agents
AI Security Review
scanned 18d ago · by lpm-firewall-aiThe static alerts map to source for ordinary CLI, repository, and runner behavior. The package has no install hook, and the inspected shell execution depends on an operator-configured restart command; no concrete attack behavior was established.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The user invokes the CLI or an already configured runner restart/update flow.
Impact
These paths provide expected CLI and runner functions; inspected evidence does not establish unauthorized execution, credential transfer, or destructive behavior.
Mechanism
The CLI launches the configured restart command in restart mode; the artifact runner starts its selected engine for a run.
AI rationale
The static alerts map to source for ordinary CLI, repository, and runner behavior. The package has no install hook, and the inspected shell execution depends on an operator-configured restart command; no concrete attack behavior was established.
Decision evidence
public snapshotAI called this Clean at 90.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json exposes a CLI entrypoint and build scripts, with no install lifecycle hook.
- The local artifact runner launches the selected engine with run-specific arguments in its scratch directory.
- The shell restart branch uses an operator-configured command and is reached only for that configured restart mode.
- Repository setup preserves non-empty owner folders instead of deleting or cloning into them.
- Bootstrap checks for updates only when the user invokes the `up` command.
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 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.100.
See all versions of @proagentstore/cli for other recorded verdicts.
- Review the evidence and your use of @proagentstore/cli@0.4.100 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.