registry / @proagentstore/cli / 0.4.158
@proagentstore/cli@0.4.158
CLI for creating, publishing, and running ProAgentStore agents
AI Security Review
scanned 17d ago · by lpm-firewall-aiThe manifest has no install hook, and the inspected network, update, and process behavior is tied to user-invoked CLI operations and package-aligned workflows. Scanner signals alone do not establish malicious behavior.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The self-update check runs when a user invokes `pags up`; site-builder workers start for a task turn.
Impact
No unauthorized data transfer, destructive behavior, or unrequested account action was established.
Mechanism
The CLI checks for and installs a newer release of itself. Site-builder requests send a run-scoped token to the validated PAGS broker route.
AI rationale
The manifest has no install hook, and the inspected network, update, and process behavior is tied to user-invoked CLI operations and package-aligned workflows. Scanner signals alone do not establish malicious behavior.
Network endpoints1
api.proagentstore.online/v1/site-builder/broker/
Decision evidence
public snapshotAI called this Clean at 89.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json exposes the `pags` command and lists only build, development, and typecheck scripts; it has no install lifecycle hook.
- The bootstrap checks for an update when the user runs `pags up`, unless running from source or updates are disabled.
- Updates install another release of this CLI into its payload cache.
- Automatic runner updates default to disabled unless an existing policy enables them.
- The site builder sends its run token to a validated, per-run PAGS broker endpoint when a task turn starts.
- Repository setup refuses to clone into a nonempty directory that is not a checkout.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShellWebSocket
HighEntropyStringsUrlStrings
Source & flagged code
9 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.156
matchedIdentity = npm:QHByb2FnZW50c3RvcmUvY2xp:0.4.156
similarity = 0.943
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 unpkg1540if (restarter === "command") {
L1541: deps.spawn(process.env[RESTART_COMMAND_ENV], { shell: true, detached: true, stdio: "ignore", env: process.env }).unref();
L1542: deps.exit(0);
Findings
1 Critical6 High5 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
HighSandbox Evasion Gated Capabilitydist/index.js
HighSemantic Analysis Limiteddist/browser-runner/coding/repo.js#virtual:normalized:round1
MediumDynamic Requiredist/browser-runner/coding/runtime.js
MediumNetwork
MediumEnvironment Vars
MediumInstall Persistencedist/index.js
MediumStructural Risk Force Deep Review
Affected versions and remediation
This report applies to @proagentstore/cli@0.4.158.
See all versions of @proagentstore/cli for other recorded verdicts.
- Review the evidence and your use of @proagentstore/cli@0.4.158 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.