@proagentstore/cli@0.4.141
CLI for creating, publishing, and running ProAgentStore agents
AI Security Review
scanned 18d ago · by lpm-firewall-aiSource inspection found no install lifecycle hook or concrete attack behavior. The flagged shell, network, and environment operations support explicit CLI and runner features, including an update check gated on `up`.
Decision evidence
public snapshot- package.json declares build, dev, and typecheck scripts, with no install lifecycle hook.
- dist/bootstrap.js checks for an update only when the user invokes the `up` command; the package is installed into a versioned cache.
- dist/browser-runner/site-builder/runtime.js validates that the broker URL belongs to the PAGS broker and the specific run.
- dist/index.js uses a configured restart command only in the runner restart path.
- dist/browser-runner/coding/repo.js runs SSH in batch mode with a timeout to probe repository identity.
- The inspected source contains process execution, network access, and environment reads, but these appear in explicit CLI, runner, and repository workflows; no concrete attack behavior was identified.
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.141.
See all versions of @proagentstore/cli for other recorded verdicts.
- Review the evidence and your use of @proagentstore/cli@0.4.141 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.