@proagentstore/cli@0.4.139
CLI for creating, publishing, and running ProAgentStore agents
AI Security Review
scanned 18d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and inspected runtime paths constrain service credentials and subprocess use to CLI features or explicit configuration. Scanner indicators are consistent with those behaviors and do not establish a concrete attack.
Decision evidence
public snapshot- package.json exposes the CLI through dist/bootstrap.js and lists only build, dev, and typecheck scripts; it has no install lifecycle hook.
- The site-builder runtime restricts its broker URL to the PAGS broker for that run and sends the run token there.
- The shell restart path is selected only when PAGS_RESTART_COMMAND is configured; the package uses that configured value to restart the runner.
- The repository helper leaves a non-empty owner directory untouched or refuses to clone into it.
- Login validates the received session against the package’s PAGS API before saving it.
- The source contains subprocess execution, network requests, and environment-variable access, but the inspected callers use these for CLI features, local agent tasks, and configured runner management.
- The scanner’s shell and command-output indicators do not establish an automatic install action or an unconsented credential transfer.
Source & flagged code
7 flaggedPackage source references child process execution.
dist/browser-runner/site-builder/runtime.jsView on unpkg · L32This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/index.jsView on unpkgFindings
Affected versions and remediation
This report applies to @proagentstore/cli@0.4.139.
See all versions of @proagentstore/cli for other recorded verdicts.
- Review the evidence and your use of @proagentstore/cli@0.4.139 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.