@proagentstore/cli@0.4.185
CLI for creating, publishing, and running ProAgentStore agents
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe scanner’s credential and execution flags correspond to provider-specific model-list requests, ProAgentStore authentication, and GitHub runner management. The manifest has no install hook, and the inspected automatic update check is limited to the explicit `up` command.
Decision evidence
public snapshot- The manifest describes a CLI for creating, publishing, and running ProAgentStore agents and declares no install lifecycle scripts.
- The bootstrap checks for updates only when the user runs `up`; it fetches the CLI’s own payload.
- Model-list requests use the corresponding provider’s API and an existing provider key, for the purpose of retrieving that provider’s models.
- GitHub Actions runner installation is handled by an explicit install operation, consistent with the package’s runner-management purpose.
- Device login sends its sign-in request to the configured ProAgentStore API.
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.185.
See all versions of @proagentstore/cli for other recorded verdicts.
- Review the evidence and your use of @proagentstore/cli@0.4.185 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.