@proagentstore/cli@0.4.176
⚠ Under reviewCLI for creating, publishing, and running ProAgentStore agents
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe inspected package source did not establish malicious behavior, and the install-time manifest has no lifecycle hooks. The declared Playwright dependency remains unresolved, so its behavior cannot be cleared from source inspection alone.
Decision evidence
public snapshot- The manifest declares Playwright as a runtime dependency, and the package has browser-related runtime code that may use it.
- Running `pags up` can check for and install a newer CLI payload; this update behavior is limited to that command.
- The actions runner downloads and configures a GitHub runner as part of its install operation.
- The manifest declares no lifecycle scripts that run during package installation.
- The inspected runner installation code is an explicit install operation and downloads the runner from GitHub.
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.176.
See all versions of @proagentstore/cli for other recorded verdicts.
- Review the evidence and your use of @proagentstore/cli@0.4.176 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.