@proagentstore/cli@0.4.143
CLI for creating, publishing, and running ProAgentStore agents
AI Security Review
scanned 18d ago · by lpm-firewall-aiThe flagged shell, network, and environment operations are part of user-invoked CLI and runner behavior; source inspection found no concrete attack path. Credentials are sent to the intended ProAgentStore service or a run-specific broker validated against that service.
Decision evidence
public snapshot- The manifest exposes a CLI entrypoint and contains no install lifecycle hook.
- Login validates a session with the ProAgentStore API and stores it for later CLI use.
- The MCP proxy defaults to the ProAgentStore MCP service and runs only when its command is invoked.
- The website builder checks that its broker URL matches the run-specific ProAgentStore broker and sends its token there.
- Repository setup refuses to overwrite non-empty user directories and invokes Git with argument arrays.
- Background mode constructs a restart command from the current Node executable and CLI arguments.
- Runner restart uses a shell, but only for the configured restart command; background startup constructs that command from the Node executable and CLI arguments.
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.143.
See all versions of @proagentstore/cli for other recorded verdicts.
- Review the evidence and your use of @proagentstore/cli@0.4.143 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.