@proagentstore/cli@0.4.198
CLI for creating, publishing, and running ProAgentStore agents
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe flagged shell, browser, and network behavior supports the package’s stated agent CLI and runner functionality. Credential use observed is directed to the corresponding provider, while reuse of the real Chrome profile is explicitly gated.
Decision evidence
public snapshot- The manifest exposes a CLI entry point and declares no install lifecycle hook.
- Engine model lookup sends a provider key to that engine provider’s own models endpoint.
- Using the real Chrome profile requires an explicit environment setting or profile path.
- Runner update diagnostics are masked, capped, and included in platform status reports.
- The package runs browser automation, shell commands, and a GitHub Actions runner, which account for the flagged process execution and network activity.
- The CLI uploads update logs to its own platform as runner status diagnostics.
Source & flagged code
10 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.198.
See all versions of @proagentstore/cli for other recorded verdicts.
- Review the evidence and your use of @proagentstore/cli@0.4.198 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.