@proagentstore/cli@0.4.160
CLI for creating, publishing, and running ProAgentStore agents
AI Security Review
scanned 17d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and inspected network and process behavior is associated with user-run CLI and runner functions. The scanner's shell, process, environment, and network signals correspond to these product operations; the inspected source did not establish an attack surface.
Decision evidence
public snapshot- The package exposes a CLI and payload entrypoint; its listed scripts are build, dev, and typecheck, with no install lifecycle hook.
- The launcher checks for updates only when the user runs `up`, and skips the check for source runs or when the opt-out is set.
- The API base defaults to the ProAgentStore service; runner traffic defaults to localhost.
- The site-builder broker route is on the ProAgentStore API host.
- Repository cloning uses git with the supplied clone URL and disables interactive prompts.
- The headless runner starts the configured engine in its configured work directory with the engine environment.
Source & flagged code
9 flaggedPackage source references child process execution.
dist/browser-runner/site-builder/runtime.jsView on unpkg · L32Findings
Affected versions and remediation
This report applies to @proagentstore/cli@0.4.160.
See all versions of @proagentstore/cli for other recorded verdicts.
- Review the evidence and your use of @proagentstore/cli@0.4.160 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.