@proagentstore/cli@0.4.126
CLI for creating, publishing, and running ProAgentStore agents
AI Security Review
scanned 18d ago · by lpm-firewall-aiThe inspected source ties the flagged operations to CLI functions and shows no install-time attack behavior. The login token is sent to the configured ProAgentStore API, and repository cloning uses the supplied URL with guards for existing directories.
Decision evidence
public snapshot- package.json exposes a CLI entrypoint; its scripts define build, development, and type-check commands, with no install lifecycle hook.
- The native preflight uses fixed system probes to report platform permissions and available devices.
- Login sends the session token to the package’s configured ProAgentStore API for validation.
- Repository setup reuses existing checkouts, guards non-empty directories, and uses the supplied clone URL only when cloning is needed.
- The scanner’s shell, process, environment, and network matches are consistent with the CLI’s update, diagnostic, authentication, and repository functions; they do not establish an attack.
Source & flagged code
7 flaggedPackage source references child process execution.
dist/browser-runner/native/preflight.jsView on unpkg · L17This 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.126.
See all versions of @proagentstore/cli for other recorded verdicts.
- Review the evidence and your use of @proagentstore/cli@0.4.126 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.