@proagentstore/cli@0.4.134
CLI for creating, publishing, and running ProAgentStore agents
AI Security Review
scanned 18d ago · by lpm-firewall-aiThe API wrapper accepts an unrestricted configured base and can use the saved PAGS session token for requests, creating a conditional credential exposure risk. The default endpoint is the PAGS API, and no source evidence supports blocking the package.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A signed-in user runs an API-backed CLI command while PAGS_API_BASE is set.
Impact
A configured third-party host could receive the saved session token. The source establishes conditional exposure, not an unrelated publisher-selected default or malicious intent.
Mechanism
The shared request wrapper can attach the saved session token as a bearer credential and send it to the selected API base.
AI rationale
The API wrapper accepts an unrestricted configured base and can use the saved PAGS session token for requests, creating a conditional credential exposure risk. The default endpoint is the PAGS API, and no source evidence supports blocking the package.
Evidence
dist/index.js
Network endpoints1
api.proagentstore.online
Decision evidence
public snapshotAI called this Suspicious at 88.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The manifest exposes a user-run CLI and lists build, development, and type-check scripts without an install hook.
- The API base uses PAGS_API_BASE when set and otherwise defaults to https://api.proagentstore.online.
- The request header can fall back to a locally saved session token.
- The shared request wrapper requires authorization and sends requests to the selected API base; a signed-in machine-name removal command calls it with the saved session token.
- Initial sign-in validates the received session token against the PAGS authentication API.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShellWebSocket
HighEntropyStringsUrlStrings
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.134.
See all versions of @proagentstore/cli for other recorded verdicts.
- Review the evidence and your use of @proagentstore/cli@0.4.134 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.