@proagentstore/cli@0.4.164
CLI for creating, publishing, and running ProAgentStore agents
AI Security Review
scanned 16d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the reviewed execution sites are tied to CLI runner tasks. The scanner signals are consistent with the package's stated runner functionality and do not establish malicious behavior.
Decision evidence
public snapshot- The manifest names a CLI entry point and lists only build, development, and typecheck scripts.
- Runner restarts are handled according to the active service or launcher mode.
- The site builder removes its broker token from stored task input and keeps it in per-run storage.
- The Actions runner downloads and configures the GitHub runner as part of a requested install job.
- Repository cloning uses Git with the requested URL and branch.
- Capture artifacts are restricted to the platform API host.
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/actions-runner.jsView on unpkg · L138Findings
Affected versions and remediation
This report applies to @proagentstore/cli@0.4.164.
See all versions of @proagentstore/cli for other recorded verdicts.
- Review the evidence and your use of @proagentstore/cli@0.4.164 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.