@proagentstore/cli@0.4.165
CLI for creating, publishing, and running ProAgentStore agents
AI Security Review
scanned 16d ago · by lpm-firewall-aiThe flagged execution and network behavior is part of the package’s runner and repository features, activated through CLI or task operations. The manifest has no install hook, and the inspected source showed no concrete attack behavior.
Decision evidence
public snapshot- The manifest exposes the `pags` command and has no install lifecycle hook.
- The browser runner starts through the explicit `up` command; its restart path logs and relaunches that command.
- Website Builder broker requests are restricted to the PAGS broker URL for the specific run.
- Actions runner setup validates a GitHub organization or repository URL and a caller-provided runner token.
- Repository handling reuses existing checkouts and confines work directories; cloning occurs only when a clone URL is supplied.
- Coding inspection confines requested work directories to the session checkout or managed repository area.
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.165.
See all versions of @proagentstore/cli for other recorded verdicts.
- Review the evidence and your use of @proagentstore/cli@0.4.165 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.