@proagentstore/cli@0.4.179
CLI for creating, publishing, and running ProAgentStore agents
AI Security Review
scanned 12d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the update path is activated by running `pags up`. The flagged network and process capabilities are consistent with the CLI's runner and browser features; the inspected source does not establish a concrete attack surface.
Decision evidence
public snapshot- package.json exposes the `pags` command and lists build and development scripts, with no install lifecycle hook.
- The launcher checks for updates only when the user runs `pags up`; it installs updates into a separate package cache.
- The inspected dependencies provide MCP client/server transports and Playwright browser automation.
- Runner setup validates a GitHub organization or repository URL and starts only through a requested runner job; the inspected repository and terminal modules support those runner features.
- The site builder uses a run-specific ProAgentStore broker, and Windows runner setup is platform-gated.
- The dependency manifest identifies @playwright/mcp version 0.0.77 as Playwright tools for MCP.
- The package can download and execute updated releases when `pags up` is run.
- Runner features download and configure a GitHub Actions runner and support local process execution; the inspected source ties these operations to runner jobs and validated targets.
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/windows-runner-live.jsView on unpkg · L59Findings
Affected versions and remediation
This report applies to @proagentstore/cli@0.4.179.
See all versions of @proagentstore/cli for other recorded verdicts.
- Review the evidence and your use of @proagentstore/cli@0.4.179 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.