@proagentstore/cli@0.4.203
CLI for creating, publishing, and running ProAgentStore agents
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe flagged behaviors are consistent with the CLI's stated purpose: provider keys are used against their own APIs for model lists, and git is used for requested repository clones. No install hook or automatic unrelated credential transfer was found in the reviewed paths.
Decision evidence
public snapshot- package.json exposes a CLI executable and declares no lifecycle scripts.
- Provider keys are sent to their matching provider API only to retrieve model lists.
- The added clone-evidence code runs git checks to verify a requested GitHub clone.
- Clone jobs use GitHub HTTPS or SSH and do not embed credentials in clone URLs.
- The `up` command requires a ProAgentStore session before fetching the user's instances.
- Service installation is performed through an explicit `--install-service` command option.
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.203.
See all versions of @proagentstore/cli for other recorded verdicts.
- Review the evidence and your use of @proagentstore/cli@0.4.203 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.