@proagentstore/cli@0.4.167
CLI for creating, publishing, and running ProAgentStore agents
AI Security Review
scanned 15d ago · by lpm-firewall-aiSource inspection found no concrete attack behavior. The scanner’s execution and network signals correspond to user-invoked CLI and runner operations, while the manifest has no install hook.
Decision evidence
public snapshot- The manifest exposes a CLI entrypoint and declares only build, development, and typecheck scripts; it has no install lifecycle hook. Its inspected dependencies are Commander and Chalk.
- Login validates the saved session token against the package’s PAGS API and stores the resulting session for CLI use.
- The launcher checks for an update only when the `up` command is invoked.
- Inspected process execution launches a configured coding engine; repository cloning targets a specified work directory, and terminal capture targets a selected local session.
- The GitHub runner setup function validates its request and target before starting a runner job.
- The broker URL is restricted to the PAGS site-builder endpoint; the reviewed source showed no unintended credential transfer or install-time mutation.
Source & flagged code
9 flaggedPackage source references child process execution.
dist/browser-runner/site-builder/runtime.jsView on unpkg · L32Package source references shell execution.
dist/browser-runner/coding/actions-runner.jsView on unpkg · L138Findings
Affected versions and remediation
This report applies to @proagentstore/cli@0.4.167.
See all versions of @proagentstore/cli for other recorded verdicts.
- Review the evidence and your use of @proagentstore/cli@0.4.167 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.