@proagentstore/cli@0.4.140
CLI for creating, publishing, and running ProAgentStore agents
AI Security Review
scanned 18d ago · by lpm-firewall-aiThe source inspection found no lifecycle hook or concrete attack behavior. The scanner's execution and network signals correspond to CLI functions, including self-update gated on an explicit command.
Decision evidence
public snapshot- The package exposes a CLI entrypoint and a bundled payload; no lifecycle install hooks are declared.
- The site builder uses a fixed ProAgentStore broker endpoint for its calls.
- The runner sends its session token to the ProAgentStore API to fetch the signed-in user's instances.
- The coding repository check runs a bounded Git status query in the selected work directory.
- Self-update is checked only for the explicit `up` command; the payload installer fetches a specified release into the CLI cache.
Source & flagged code
7 flaggedPackage source references child process execution.
dist/browser-runner/site-builder/runtime.jsView on unpkg · L32This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/index.jsView on unpkgFindings
Affected versions and remediation
This report applies to @proagentstore/cli@0.4.140.
See all versions of @proagentstore/cli for other recorded verdicts.
- Review the evidence and your use of @proagentstore/cli@0.4.140 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.