@proagentstore/cli@0.4.190
CLI for creating, publishing, and running ProAgentStore agents
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe flagged capabilities are consistent with a CLI that runs agents and manages runners, and the inspected credential flows go to the relevant service or matching provider. I found no install-time behavior or concrete malicious exfiltration in the reviewed source.
Decision evidence
public snapshot- The manifest describes a CLI for creating, publishing, and running ProAgentStore agents; its bin is the bootstrap CLI.
- The saved session token is validated against api.proagentstore.online, the package’s own service.
- Engine model discovery sends Anthropic and OpenAI keys only to their matching providers’ model-list endpoints; the code says the key is used for that request and not returned.
- The Actions runner installer downloads releases from GitHub’s official actions/runner release path.
- The package exposes command execution, a WebSocket relay, and persistent runner/service options, which are powerful capabilities but fit its agent-runner purpose.
- There are no install, preinstall, or postinstall lifecycle hooks in the manifest.
- The scanner’s credential-host leads resolve to provider-matching model-list calls or ordinary GitHub token handling, not evidence of unrelated credential exfiltration.
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.190.
See all versions of @proagentstore/cli for other recorded verdicts.
- Review the evidence and your use of @proagentstore/cli@0.4.190 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.