@proagentstore/cli@0.4.152
CLI for creating, publishing, and running ProAgentStore agents
AI Security Review
scanned 18d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the reviewed updater is command-triggered and installs another release of the same CLI. The inspected runtime hints and required source paths show product-aligned behavior without a confirmed attack surface.
Decision evidence
public snapshot- package.json defines a CLI entrypoint and build, development, and typecheck scripts, with no lifecycle hook.
- The hinted restart operation selects a restart mode and exits or hands control to the launcher; this excerpt shows no unrelated account action.
- The site-builder runtime identifies the PAGS broker as the destination for its broker credential.
- The coding repository check runs a bounded git status query in the selected work directory.
- The launcher checks for updates only when the user runs `pags up`; the update code fetches and caches a release of this same CLI.
Source & flagged code
9 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.152.
See all versions of @proagentstore/cli for other recorded verdicts.
- Review the evidence and your use of @proagentstore/cli@0.4.152 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.