registry / @proagentstore/cli / 0.4.162
@proagentstore/cli@0.4.162
CLI for creating, publishing, and running ProAgentStore agents
AI Security Review
scanned 17d ago · by lpm-firewall-aiThe source inspection found no install lifecycle hook or concrete attack chain. Flagged shell, network, and execution capabilities are tied to CLI update, authentication, and task workflows.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Login, `pags up`, or a runner task.
Impact
No unintended credential disclosure, destructive action, or persistence was identified.
Mechanism
The inspected code validates sessions against the package's service and runs task-scoped tooling; no unrelated credential recipient or unconsented install-time action was established.
AI rationale
The source inspection found no install lifecycle hook or concrete attack chain. Flagged shell, network, and execution capabilities are tied to CLI update, authentication, and task workflows.
Network endpoints1
api.proagentstore.online
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 lists build, dev, and typecheck scripts; no install lifecycle hook is present.
- The launcher checks for updates only when the command is up.
- Login stores sessions under the ProAgentStore config directory and validates them against api.proagentstore.online.
- Website Builder launches an engine for a task and uses a run-scoped bridge token.
- The actions runner installs GitHub's runner as a job; its command arguments mask the supplied token in job logs.
- Repository setup refuses to clone into a non-empty directory without a Git 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/browser-runner/coding/actions-runner.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = @proagentstore/cli@0.4.161
matchedIdentity = npm:QHByb2FnZW50c3RvcmUvY2xp:0.4.161
similarity = 0.989
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/browser-runner/coding/actions-runner.jsView on unpkgFindings
1 Critical6 High5 Medium4 Low
CriticalPrevious Version Dangerous Deltadist/browser-runner/coding/actions-runner.js
HighChild Processdist/browser-runner/site-builder/runtime.js
HighShelldist/browser-runner/coding/actions-runner.js
HighSame File Env Network Executiondist/index.js
HighCommand Output Exfiltrationdist/index.js
HighSandbox Evasion Gated Capabilitydist/browser-runner/coding/actions-runner.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
Affected versions and remediation
This report applies to @proagentstore/cli@0.4.162.
See all versions of @proagentstore/cli for other recorded verdicts.
- Review the evidence and your use of @proagentstore/cli@0.4.162 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.