@proagentstore/cli@0.4.142
CLI for creating, publishing, and running ProAgentStore agents
AI Security Review
scanned 18d ago · by lpm-firewall-aiSource inspection found no install hook or concrete attack behavior. The flagged network, process execution, and credential handling are tied to explicit CLI or runner functions and scoped destinations.
Decision evidence
public snapshot- The manifest exposes a CLI entrypoint and lists only build, dev, and typecheck scripts; it has no install lifecycle hook.
- The bootstrap checks for updates only when the user invokes the up command.
- Login validates the returned session against the fixed ProAgentStore API.
- The site-builder binds its broker credential to the ProAgentStore broker URL for the specific run and restricts available tools; deployment requires owner approval.
- Shell restart execution requires PAGS_RESTART_COMMAND to be set, and clone credentials are used only for HTTPS clone URLs.
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.142.
See all versions of @proagentstore/cli for other recorded verdicts.
- Review the evidence and your use of @proagentstore/cli@0.4.142 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.