@proagentstore/cli@0.4.153
CLI for creating, publishing, and running ProAgentStore agents
AI Security Review
scanned 18d ago · by lpm-firewall-aiSource inspection found no install-time hook or concrete attack behavior. The scanner's dynamic loading, process, and network signals align with the CLI launcher and runtime functions inspected.
Decision evidence
public snapshot- The manifest exposes a CLI entrypoint and defines no install lifecycle hooks.
- The inspected runtime operation exits or restarts the process according to its launcher mode.
- The site-builder runtime stores a run's broker credential separately from the stored task input.
- Repository credential handling is limited to HTTPS URLs, avoiding credential injection into SSH URLs.
- The launcher checks for updates when the selected command is `up`; the inspected payload installation uses the named package and version.
Source & flagged code
9 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.153.
See all versions of @proagentstore/cli for other recorded verdicts.
- Review the evidence and your use of @proagentstore/cli@0.4.153 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.