@proagentstore/cli@0.4.114
CLI for creating, publishing, and running ProAgentStore agents
AI Security Review
scanned 18d ago · by lpm-firewall-aiThe manifest has no install lifecycle hooks, and the inspected process and network behavior is tied to CLI or runner workflows. The scanner flags do not establish a concrete attack surface.
Decision evidence
public snapshot- package.json exposes a CLI entrypoint and does not define install lifecycle hooks.
- The bootstrap checks for updates only for the explicit `up` command and loads the selected CLI payload.
- The local artifact runtime starts the configured engine process for a task run.
- The runner restart path uses the configured restart command when that restarter is selected.
- The repository check runs a fixed Git inspection command in the requested directory.
- The `up` workflow sends the saved session token to the ProAgentStore API to fetch the user's instances.
Source & flagged code
7 flaggedPackage source references child process execution.
dist/browser-runner/local-artifact/runtime.jsView on unpkg · L22This 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.114.
See all versions of @proagentstore/cli for other recorded verdicts.
- Review the evidence and your use of @proagentstore/cli@0.4.114 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.