@proagentstore/cli@0.4.191
CLI for creating, publishing, and running ProAgentStore agents
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe reviewed network requests use the package's API or the relevant AI provider, and the command execution supports runner setup. The package declares no install lifecycle hook, and the routing flags did not establish unrelated exfiltration or unauthorized actions.
Decision evidence
public snapshot- The visible npm scripts are build, dev, typecheck, and test:package; no install hook appears in package.json.
- The CLI describes `pags up` as starting the browser runner for the user's agent instances.
- `pags up` fetches the signed-in user's instances from the package's API using the stored session token.
- The engine model-list helper uses a provider API key for a model-list request and states that the key is not returned.
- Actions-runner installation executes supplied setup steps while masking the registration token in recorded commands.
Source & flagged code
10 flaggedPackage source references child process execution.
dist/browser-runner/site-builder/runtime.jsView on unpkg · L32Package source references shell execution.
dist/browser-runner/coding/windows-runner-live.jsView on unpkg · L59Findings
Affected versions and remediation
This report applies to @proagentstore/cli@0.4.191.
See all versions of @proagentstore/cli for other recorded verdicts.
- Review the evidence and your use of @proagentstore/cli@0.4.191 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.