@proagentstore/cli@0.4.138
CLI for creating, publishing, and running ProAgentStore agents
AI Security Review
scanned 18d ago · by lpm-firewall-aiThe manifest has no install hook, and the reviewed runtime paths show product-aligned API and broker use with a run-matched broker destination. The scanner's execution and network signals correspond to runner and repository operations; they do not establish malicious behavior.
Decision evidence
public snapshot- package.json lists build, development, and type-check scripts; it has no install lifecycle hook.
- The site builder validates the broker URL against the PAGS broker route for the matching run, then sends broker requests to that URL.
- The PAGS API client defaults to api.proagentstore.online and resolves a PAGS token from explicit input, the environment, or a saved session.
- Repository inspection runs git rev-parse in the selected work directory with a timeout; no modification is shown.
- The bootstrap checks for an update only for the explicit up command.
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.138.
See all versions of @proagentstore/cli for other recorded verdicts.
- Review the evidence and your use of @proagentstore/cli@0.4.138 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.