registry / @proagentstore/cli / 0.4.119
@proagentstore/cli@0.4.119
CLI for creating, publishing, and running ProAgentStore agents
AI Security Review
scanned 18d ago · by lpm-firewall-aiStatic hints point to ordinary CLI and runner functionality, and the inspected source supports those uses. The package declares no install lifecycle hook, and the reviewed credential and process operations are scoped to their intended functions.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Normal CLI use; update checking requires the user to invoke `pags up`.
Impact
No confirmed unauthorized credential transfer, destructive behavior, or install-time mutation was established.
Mechanism
The inspected code scopes git inspection to the selected work directory, writes local artifacts as new files, and validates saved sessions against the package API.
AI rationale
Static hints point to ordinary CLI and runner functionality, and the inspected source supports those uses. The package declares no install lifecycle hook, and the reviewed credential and process operations are scoped to their intended functions.
Network endpoints1
api.proagentstore.online
Decision evidence
public snapshotAI called this Clean at 92.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json exposes the CLI entrypoint and lists only build, dev, and typecheck scripts; no install lifecycle hook is declared.
- The local artifact runtime writes generated files exclusively into its run output area.
- Saved session credentials are sent to the package’s ProAgentStore API for session validation.
- Repository inspection runs git with the selected work directory as its current directory.
- The bootstrap checks for an update 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 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.119.
See all versions of @proagentstore/cli for other recorded verdicts.
- Review the evidence and your use of @proagentstore/cli@0.4.119 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.